I am trying to use the following code to handle an exception in
Turbogears, but it does not grab the SQLError:
please note I did a:
from sqlalchemy.exceptions import SQLError
def save(self, name=None, email=None, password=None,
password_confirm=None,
**kw):
try:
Michael,
I got some errors (NoSuchColumnError) after upgrading SA from 0.3.6 to 0.3.7
After some research in mailing list history, I found this thread [1]:
I modified my sqlalchemy/databases/firebird.py :
---
class FBDialect(...
...
def
On May 8, 2007, at 1:23 PM, noah.gift wrote:
I am trying to use the following code to handle an exception in
Turbogears, but it does not grab the SQLError:
please note I did a:
from sqlalchemy.exceptions import SQLError
def save(self, name=None, email=None, password=None,
Hi,
I'm randomly getting InterfaceError exceptions in my app while doing a
simple query.get_by(Uid=user_id) I don't even know where to start to
look about this, I found nothing in the docs. Any pointers to the
direction I should take?
Thanks,
Hi,
Produce the simplest program you can that causes the error, then post
both the code and full exception here.
Paul
Gambit wrote:
Hi,
I'm randomly getting InterfaceError exceptions in my app while doing a
simple query.get_by(Uid=user_id) I don't even know where to start to
look about
Produce the simplest program you can that causes the error, then post
both the code and full exception here.
Paul
Sorry about the wrong subject in the last post. Google groups are quite
annoying.
This is the minimal program that causes the error:
db =
On May 8, 2007, at 2:41 PM, Gambit wrote:
Sorry about the wrong subject in the last post. Google groups are
quite
annoying.
This is the minimal program that causes the error:
db = sa.create_engine('mysql://myuser:[EMAIL PROTECTED]/
mydatabase')
metadata = sa.BoundMetaData(db)
def
Thanks for the reply. You are probably right about those things don't
belonging together, it certainly makes a lot of sense now you mention
it. I'll reorganize my code better and see if the errors go away.
Thanks!
--~--~-~--~~~---~--~~
You received this
On May 8, 1:58 pm, Michael Bayer [EMAIL PROTECTED] wrote:
On May 8, 2007, at 1:23 PM, noah.gift wrote:
I am trying to use the following code to handle an exception in
Turbogears, but it does not grab the SQLError:
please note I did a:
from sqlalchemy.exceptions import SQLError
Forgive the dumb question, but what is the proper SQLAlchemy
recommended way to deal with a situation like this.
Should I see if the object already exists first, or be lazy and try to
write to the database and attempt to catch the exception.
Good question. Personally I think that this
On May 8, 2007, at 5:45 PM, noah.gift wrote:
On May 8, 1:58 pm, Michael Bayer [EMAIL PROTECTED] wrote:
On May 8, 2007, at 1:23 PM, noah.gift wrote:
I am trying to use the following code to handle an exception in
Turbogears, but it does not grab the SQLError:
please note I did a:
11 matches
Mail list logo
