drew
>>>>>>
>>>>>>
>>>>>> On Wed, May 14, 2014 at 8:00 AM, Jeremy Dunck
>>>>>> wrote:
>>>>>>
>>>>>>> How about adding a flag to Operations? implied_null, perhaps.
>
ns? implied_null, perhaps.
>>>>>> On May 14, 2014 7:52 AM, "Andrew Godwin" wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> That's currently the only approach I'm afraid - there's a
I'm afraid - there's an open issue
>>>>>> (raised by Shai Berger I believe) that column_sql should be broken down
>>>>>> into more component pieces so it can be more easily changed, but that's
>>>>>> a
>>>>>> difficult
be more easily changed, but that's a
>>>>> difficult task to do and not something I want to go and change completely
>>>>> as we're trying to release 1.7.
>>>>>
>>>>> What we could do is change those NULL and NOT NULL strings to be
>>
easily changed, but that's a
>>>> difficult task to do and not something I want to go and change completely
>>>> as we're trying to release 1.7.
>>>>
>>>> What we could do is change those NULL and NOT NULL strings to be
>>>> def
_null_suffix =
>>> "" or similar - do you think that would be a reasonable approach?
>>>
>>> Andrew
>>>
>>>
>>> On Wed, May 14, 2014 at 7:05 AM, maxi wrote:
>>>
>>>> Hi,
>>>>
>>>> I'm tryi
reasonable approach?
>
> Andrew
>
>
> On Wed, May 14, 2014 at 7:05 AM, maxi wrote:
> Hi,
>
> I'm trying to implement the new schema migration of django 1.7 for
> django-firebird backend.
> In column_sql method, when the field can be null, in firebird,
imilar - do you think that would be a reasonable approach?
>>
>> Andrew
>>
>>
>> On Wed, May 14, 2014 at 7:05 AM, maxi wrote:
>>
>>> Hi,
>>>
>>> I'm trying to implement the new schema migration of django 1.7 for
>>> django-f
ed
> on the schema editor class itself, and then you could set sql_null_suffix =
> "" or similar - do you think that would be a reasonable approach?
>
> Andrew
>
>
> On Wed, May 14, 2014 at 7:05 AM, maxi wrote:
>
>> Hi,
>>
>> I'm trying to implemen
ay 14, 2014 at 7:05 AM, maxi wrote:
> Hi,
>
> I'm trying to implement the new schema migration of django 1.7 for
> django-firebird backend.
> In column_sql method, when the field can be null, in firebird, is not
> necessary add the NULL keyword. So to change this behavior I n
Hi,
I'm trying to implement the new schema migration of django 1.7 for
django-firebird backend.
In column_sql method, when the field can be null, in firebird, is not
necessary add the NULL keyword. So to change this behavior I need override
the entire column_sql method just to change one
Maxi,
I do have a few bugfixes for the firebird-backend. How can we get in
touch?
Regards,
Thomas
On Sep 28, 11:26 pm, maxi wrote:
> Hi,
> I'm working on implementation of firebird backend for django [1]
> I've an issue related of icontains filter option. Firebird uses
> CONTAINING sql claus
On Mon, Sep 28, 2009 at 6:26 PM, maxi wrote:
>
> Hi,
> I'm working on implementation of firebird backend for django [1]
> I've an issue related of icontains filter option. Firebird uses
> CONTAINING sql clause for this, which is case insesitive.
>
> The problem is that the output generated (where
Hi,
I'm working on implementation of firebird backend for django [1]
I've an issue related of icontains filter option. Firebird uses
CONTAINING sql clause for this, which is case insesitive.
The problem is that the output generated (where clause) is wrong.
It return:
WHERE "TABLE"."FIELD
14 matches
Mail list logo
