that is odd.. I did do some tests with Firebird with enterprise and row, but
have since uninstalled it :(
I would guess that "password" is a key word in Firebird's SQL dialect. Maybe
we should change that column name to something less likely to cause that
kind of conflict.
-----Original Message-----
From: twisted-python-admin at twistedmatrix.com
[mailto:twisted-python-admin at twistedmatrix.com]On Behalf Of Joshua
Ritter
Sent: Wednesday, October 23, 2002 12:14 AM
To: twisted-python at twistedmatrix.com
Subject: [Twisted-Python] dbcred and Firebird Incompatibility
First the stuff that makes sense:
---
Firebird doesn't like batched SQL statements in a single string any better
than MySQL does...
Also it doesn't like the Primary Key in dbcred's schema not being specified
as NOT NULL
In twisted_identities:
identity_name varchar(64) NOT NULL PRIMARY KEY
In twisted_services:
service_name varchar(64) NOT NULL PRIMARY KEY
---
Now for something weird...
Firebird chokes in CREATE TABLE twisted_identities on the password column...
by changing the name to identity_password it works?!?!?!?!?
-J
_______________________________________________
Twisted-Python mailing list
Twisted-Python at twistedmatrix.comhttp://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python