Export to GitHub

django-firebird - issue #5

Support for RETURNING clause?


Posted on Sep 29, 2009 by Massive Giraffe

Firebird 2 supports the RETURNING clause for returning server-side incremented values e.g. by an auto-increment trigger.

I've added support for the RETURNING clause in base.py. How do I get commit rights to add this feature?

Comment #1

Posted on Sep 29, 2009 by Grumpy Horse

Send me the patch and i will commit it , I will ask maxim to give you commit access

Comment #2

Posted on Sep 29, 2009 by Happy Panda

RETURNING clause can break Firebird 1.5 compatibility. We need to discuss how to implement this. Any idea?

Comment #3

Posted on Sep 30, 2009 by Grumpy Horse

can you upgrade to firebird 2.x latest stable is 2.1 and soon we will have 2.5

maybe we can detect if it's 1.5 then with an siple if it can work for firebird 2.1.x

also can you give him svn access ?

Comment #4

Posted on Sep 30, 2009 by Grumpy Horse

i see that svn access is granted now

Comment #5

Posted on Sep 30, 2009 by Happy Panda

Using something like this:

import kinterbasdb

dsn = 'path_to_your_db' con = kinterbasdb.connect(dsn=dsn, user='sysdba', password='masterkey', charset='ISO8859_1')

sv = con.server_version print sv print 'Just we need this:', sv[sv.index('Firebird'):]

Here we can get the firebird version as string and to use this with a "if" Is it the best approach?

Comment #6

Posted on Sep 30, 2009 by Massive Giraffe

I guess so, yes (beeing not a python export g).

The simple rule is. Firebird 1.x (1.0, 1.5) does not support RETURNING. Firebird 2.x and later does support RETURNING.

Comment #7

Posted on Jul 22, 2011 by Happy Panda

(No comment was entered for this change.)

Status: Fixed

Labels:
Type-Defect Priority-Medium