FYI I get this trace with the version you attached.
Traceback (most recent call last):
File "/home/john/sqla/sqlatest.py", line 5, in -toplevel-
fbdb = create_engine(dbstr)
File "build/bdist.linux-i686/egg/sqlalchemy/engine/__init__.py",
line 154, in create_engine
File "build/bdist.linu
johnbraduk> Using SQLAlchemy-0.3.7-py2.4 released with Turbogears
johnbraduk> """ Traceback (most recent call last): File
johnbraduk> "/var/tmp/sqlatest.py", line 3, in -toplevel- fbdb =
johnbraduk> create_engine(dbstr) File
johnbraduk> "build/bdist.linux-i686/egg/sqlalchemy/eng
Michael,
Here are the results I am getting. I am trying to get TurboGears to
work so I don't know which versions of SQLAlchemy can be used with TG
and not screw it up.
Test prog.
from sqlalchemy import *
dbstr = 'firebird://SYSDBA:[EMAIL PROTECTED]/usr/ibdata/eiti61.gdb'
fbdb = create_engine(db
Hi John,
I haven't push SA with firebird to the limit, but until now I am happy... :)
And what "other fixes" are you talking about ? I am using SA 2.7 with
firebird.py modified by changes made in Changeset 2674...
As Michael wrote above, maybe a traceback would help a lot to solve
your problem
firebird is a little like a chicken without a head at this point...im
applying fixes but have no FB database with which to test on.
what results/stack traces/everything else are you getting with the
current SQLAlchemy trunk ?
On May 31, 2007, at 3:33 PM, johnbraduk wrote:
>
> Roger,
> Plea
Roger,
Please excuse the interrupt, but have you applied other fixes? I (and
others) can't event get SQLA to connect to
my Firebird v1.5.4 database running on SUSE Linux.
John
On 30 May, 19:47, "Roger Demetrescu" <[EMAIL PROTECTED]>
wrote:
> Michael, the patch did the trick...
>
> I was able t
Michael,
On 5/30/07, Michael Bayer <[EMAIL PROTECTED]> wrote:
>
> i commited the fix for the previous issue and a probable fix for the
> current issue youre having in r2674.
Yeaph, all is running fine now... :)
> we can put a buildslave on your firebird host that would run all the
> tests ev
i commited the fix for the previous issue and a probable fix for the
current issue youre having in r2674.
we can put a buildslave on your firebird host that would run all the
tests everytime a SA checkin occurs.although we'd have to really
qualify a lot of the tests which arent support
Michael, the patch did the trick...
I was able to print the statement, execute it, and also do some
inserts using ORM...
Now the second part of my problem, which is not fixed yet... ;)
here is the script (now using default value/expression):
from datetime imp
hey roger -
the fix for that issue is trivial, however the code which it fixes is
doing something that should be done differently (that is, ensuring
that all pk columns are present in an INSERT statement). Since I
dont have FB here, can you try out the attached patch and see if it
works
Maybe the correct subject should be: "I can't print insert statement
with firebird engine" :)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to sqlalchemy@goog
11 matches
Mail list logo