Re: django-firebird backend: migrations and NULL fields

drew >>>>>> >>>>>> >>>>>> On Wed, May 14, 2014 at 8:00 AM, Jeremy Dunck >>>>>> wrote: >>>>>> >>>>>>> How about adding a flag to Operations? implied_null, perhaps. >

Re: django-firebird backend: migrations and NULL fields

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

Re: django-firebird backend: migrations and NULL fields

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

Re: django-firebird backend: migrations and NULL fields

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 >>

Re: django-firebird backend: migrations and NULL fields

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

Re: django-firebird backend: migrations and NULL fields

_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

Re: django-firebird backend: migrations and NULL fields

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,

Re: django-firebird backend: migrations and NULL fields

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

Re: django-firebird backend: migrations and NULL fields

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

Re: django-firebird backend: migrations and NULL fields

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

django-firebird backend: migrations and NULL fields

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

Re: Firebird backend for Django 1.6.x is updated (RC state)

El miércoles, 12 de febrero de 2014 15:11:33 UTC-3, Florian Apolloner escribió: > > Nice, can you also upload wheel packages? > Done! For now, just for the stable version (django-firebird with django 1.5 support) > > On Wednesday, February 12, 2014 2:19:11 PM UTC+1, mariuz wrote: >> >> Here

Re: Firebird backend for Django 1.6.x is updated (RC state)

Nice, can you also upload wheel packages? On Wednesday, February 12, 2014 2:19:11 PM UTC+1, mariuz wrote: > > Here are a few fixes for v1.6.x Release Candidate 1 commited into > master > > Fixed missing d

Firebird backend for Django 1.6.x is updated (RC state)

Here are a few fixes for v1.6.x Release Candidate 1 commited into master Fixed missing date_interval_sql implementation. #21 Fixed datetime_trunc_sql NotImplementedError. #20 Fixed missing SQLDateTimeCom

Re: firebird backend for django

Hi, I've opened a ticket for months ago - http://code.djangoproject.com/ticket/13159. Only needs a test case. David Elias On Jul 23, 10:30 pm, maxi wrote: > Hi, > > I'm working on django-firebird project and doing some modifications > for work with django 1.2 > Right now, I'm trying to pass

Re: firebird backend for django

On 23 jul, 18:58, Alex Gaynor wrote: > On Fri, Jul 23, 2010 at 4:56 PM, maxi wrote: > > > On 23 jul, 18:42, Alex Gaynor wrote: > >> On Fri, Jul 23, 2010 at 4:30 PM, maxi wrote: > >> > Hi, > > >> > I'm working on django-firebird project and doing some modifications > >> > for work with django

Re: firebird backend for django

On Fri, Jul 23, 2010 at 4:56 PM, maxi wrote: > > > On 23 jul, 18:42, Alex Gaynor wrote: >> On Fri, Jul 23, 2010 at 4:30 PM, maxi wrote: >> > Hi, >> >> > I'm working on django-firebird project and doing some modifications >> > for work with django 1.2 >> > Right now, I'm trying to pass some tests

Re: firebird backend for django

On 23 jul, 18:42, Alex Gaynor wrote: > On Fri, Jul 23, 2010 at 4:30 PM, maxi wrote: > > Hi, > > > I'm working on django-firebird project and doing some modifications > > for work with django 1.2 > > Right now, I'm trying to pass some tests running the tests suit of > > django trunk code and I f

Re: firebird backend for django

On Fri, Jul 23, 2010 at 4:30 PM, maxi wrote: > Hi, > > I'm working on django-firebird project and doing some modifications > for work with django 1.2 > Right now, I'm trying to pass some tests running the tests suit of > django trunk code and I found the next problem: > > django is trying to execu

firebird backend for django

Hi, I'm working on django-firebird project and doing some modifications for work with django 1.2 Right now, I'm trying to pass some tests running the tests suit of django trunk code and I found the next problem: django is trying to execute this sql: SELECT "AGGREGATION_BOOK"."PRICE", COUNT("AGG

Re: django-firebird backend

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 us

Re: django-firebird backend

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 probl

django-firebird backend

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: WH

Re: Firebird backend against 0.96 release and thoughts

Malcolm Tredinnick escreveu: > We could arrange for this to be possible as part of the QuerySet > refactor. I hadn't thought of doing it before, but it's not a bad idea. > Might even help things like the GIS branch, too. > > /me makes a TODO note. That would be perfect. I imagine that you will co

Re: Firebird backend against 0.96 release and thoughts

On Thu, 2007-04-26 at 04:44 -0700, David Elias wrote: > The new patch - http://code.djangoproject.com/ticket/1261 > > Like I've explained in the ticket's comments right now we can't do a > search in TextFields with: > __istartswith, __iendswith, __icontains > > These work well with VARCHAR usi

Firebird backend against 0.96 release and thoughts

The new patch - http://code.djangoproject.com/ticket/1261 Like I've explained in the ticket's comments right now we can't do a search in TextFields with: __istartswith, __iendswith, __icontains These work well with VARCHAR using LIKE and the UPPER function just like the oracle branch, but only

Firebird backend improved

I've uploaded a new patch against the oracle branch and updated the backend module. You can check http://code.djangoproject.com/ticket/1261 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group.

Re: New firebird backend using the boulder-oracle-sprint branch

Is there anything i can help with? I m don´t have much python knowledge Same with me :) but i m really interested in firebird support in django, so if i can help testing or doing something it will be a pleasure. Well you can use this patch on your projects and report bugs and enhancements.

Re: New firebird backend using the boulder-oracle-sprint branch

Thanx again, it worked perfectly now. Is there anything i can help with? I m don´t have much python knowledge but i m really interested in firebird support in django, so if i can help testing or doing something it will be a pleasure. also, is there any plans to add it in the main django release

Re: New firebird backend using the boulder-oracle-sprint branch

I was able to reproduce this error by enable the admin in the INSTALLED_APPS and in urls.py but not sync'ed to database, make sure you call manage.py syncdb to install also the admin app. Fabio Gomes escreveu: Thanx, it worked now. I was able to create the table, acess the objects, add, update

Re: New firebird backend using the boulder-oracle-sprint branch

Fabio Gomes <[EMAIL PROTECTED]> wrote: > > Thanx man, i ll test it right away. > > > > I was trying to hack your old one, but i didnt figure out why some > > generators weren´t created, so i was having some problems. > > > > -- Forwarded message -

Re: New firebird backend using the boulder-oracle-sprint branch

i ll test it right away. > > > > I was trying to hack your old one, but i didnt figure out why some > > generators weren´t created, so i was having some problems. > > > > -- Forwarded message -- > > From: David Elias <[EMAIL PROTECT

Re: New firebird backend using the boulder-oracle-sprint branch

; > -- Forwarded message -- > From: David Elias <[EMAIL PROTECTED]> > Date: Dec 18, 2006 1:14 PM > Subject: New firebird backend using the boulder-oracle-sprint branch > To: Django developers > > > > Please check http://code.djangoproject.com/ticket/1261 &

Re: New firebird backend using the boulder-oracle-sprint branch

Thanx man, i ll test it right away. I was trying to hack your old one, but i didnt figure out why some generators weren´t created, so i was having some problems. -- Forwarded message -- From: David Elias <[EMAIL PROTECTED]> Date: Dec 18, 2006 1:14 PM Subject: New fi

New firebird backend using the boulder-oracle-sprint branch

Please check http://code.djangoproject.com/ticket/1261 David Elias --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com

Re: Issues on making the firebird backend working

On 6/6/06, David Elias <[EMAIL PROTECTED]> wrote: > Adrian, assuming that you are working on database support, are any > plans that each backend may add sql statements to the sqlall output in > the future? I've got nothing against adding a backend-specific hook for altering the "sqlall" output. W

Re: Issues on making the firebird backend working

Already added the patch, for the ones that didn't know - http://code.djangoproject.com/ticket/1261 I'm trying to remove the "if settings.DATABASE_ENGINE == 'firebird'" from management.py and add some signals to use with the dispatcher. Already got this working inside the function "get_sql_create(

Re: Issues on making the firebird backend working

On 6/1/06, David Elias <[EMAIL PROTECTED]> wrote: > I've got the backend's base, create and introspection almost done. > Should i create a ticket or use this one > http://code.djangoproject.com/ticket/1261 and attach the files? Go ahead and use that existing ticket. Looking forward to your patch!

Re: Issues on making the firebird backend working

I've got the backend's base, create and introspection almost done. Should i create a ticket or use this one http://code.djangoproject.com/ticket/1261 and attach the files? David --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Goo

Re: Issues on making the firebird backend working

Adrian Holovaty wrote: > On 6/1/06, David Elias <[EMAIL PROTECTED]> wrote: > > > > Well, AS in FROM clause is not support... > > > > Thoughts, ideas...? > > Hey David, > > Sorry for the slow response -- let's take each issue one at a time. > What do you have coded so far? > > Adrian > > -- > Adri

Re: Issues on making the firebird backend working

Michael Radziej wrote: > David Elias wrote: > > Well, AS in FROM clause is not support... > > Not even in the equivalent form > > SELECT ... FROM table_name alias > > ? > > That would really suck. How do you do joins to "self" then? > > Michael With all the work i've forgot that, made a simple t

Re: Issues on making the firebird backend working

On 6/1/06, David Elias <[EMAIL PROTECTED]> wrote: > > Well, AS in FROM clause is not support... > > Thoughts, ideas...? Hey David, Sorry for the slow response -- let's take each issue one at a time. What do you have coded so far? Adrian -- Adrian Holovaty holovaty.com | djangoproject.com --~

Re: Issues on making the firebird backend working

David Elias wrote: > Well, AS in FROM clause is not support... Not even in the equivalent form SELECT ... FROM table_name alias ? That would really suck. How do you do joins to "self" then? Michael --~--~-~--~~~---~--~~ You received this message because you a

Re: Issues on making the firebird backend working

Well, AS in FROM clause is not support... Thoughts, ideas...? I think we're not going to have Firebird support in Django :p --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to thi

Issues on making the firebird backend working

Hi there, I've started working on firebird's backend and Adrian is also refactoring for the oracle support, so it's a good time to discuss this :) First, field and constraint names can't be bigger than 31 chars. In the creation.py declared for PositiveIntegerField integer CHECK("%(column)s"

Firebird backend

Anybody is going to write the firebird db backend, or is working on it?