Big +1.
I suspect this also opens the door to a significant speed improvement for
Oracle's number column handling, but I'll have to investigate further (ask me
about numbers_as_strings if you're interested in details).
Thanks for the great work,
Shai.
--
You received this message because yo
> Do we now have a consistent set of conversion methods and a clear view of
which one does what?
This does need further investigation and testing. In particular I know we
are being a bit heavy handed at the moment with a consequential performance
hit. The issue is that some backends require conver
I support deleting
django.contrib.gis.db.models.sql.compiler.SQLDateTimeCompiler. There's some
code in Django I'm really ashamed of; this class ranks high on the list.
I've been frustrated by inconsistencies in this area in the past but never
investigated. Overall, your approach looks reasonabl
I'm a big fan of the resolve_columns and convert_values cleanup. The large
swaths of removed code in GIS is also very welcome. Great stuff!
I suspect I'll be able to make a few improvements in the
aggregation/annotation patch I've been working on once this lands.
--
You received this message b
On Tuesday, August 26, 2014 8:45:03 AM UTC+2, ryan liang wrote:
>
> """
> payload = ... your payload ...
> stream = StringIO(payload)
> client.post(url,
> CONTENT_TYPE='text/json',
> CONTENT_LENGTH=len(payload),
> wsgi.input = stream)
> """
> It does not work.
>
Obviously not, wsgi.inp
"""
payload = ... your payload ...
stream = StringIO(payload)
client.post(url,
CONTENT_TYPE='text/json',
CONTENT_LENGTH=len(payload),
wsgi.input = stream)
"""
It does not work.
在 2006年10月4日星期三UTC+8上午8时46分46秒，Russell Keith-Magee写道：
>
> On 10/4/06, Mikeal Rogers > wrote:
> >
> > I'm a l
The way database values are converted to Python values really needs to
be cleaned up. Currently there are multiple different ways to do value
conversions, but for example for .values() calls none of the ways apply.
There are somewhat complicated hacks to make gis and date queries work
correctly.
T
Hi all,
This thread relates to proposed (and nearly RFC) changes in
https://github.com/django/django/pull/3047. It contains backwards
incompatible changes relevant to third party database backend authors, and
to anyone using SubfieldBase in custom fields.
*tl;dr*
Deprecation of SubfieldBase, remo
2014-08-26 9:48 GMT+02:00 Christian Schmitt :
> Is there a way to merge user accounts? Currently my github Account is
> c-schmitt, while my Trac user account ist merb.
>
Technically, there's no such thing as a Trac account, just a username
attached to tickets and comments.
I spent some time Goog
Is there a way to merge user accounts? Currently my github Account is
c-schmitt, while my Trac user account ist merb.
—
Best Regards
Christian Schmitt
c.schm...@briefdomain.de
Am 24.08.2014 um 21:52 schrieb Ben Finney :
> Aymeric Augustin
>
> writes:
>
>> Contributors who refuse GitHub
10 matches
Mail list logo
