On Oct 5, 2013, at 1:58 AM, limodou limo...@gmail.com wrote:
Today I found if I have an id column in a table, and the autoincrement
attribute is True, when I created the table it's right, but when I print the
create statment is not right for autoincrement. The testing code is:
from
Thank you very much. This fixes my problem. So it's not a bug?
On Sat, Oct 5, 2013 at 2:17 PM, Michael Bayer mike...@zzzcomputing.comwrote:
On Oct 5, 2013, at 1:58 AM, limodou limo...@gmail.com wrote:
Today I found if I have an id column in a table, and the autoincrement
attribute is True,
Thanks guys. Jonathan, that is, I think, what will be going on.
So, I'm not quite clear from your comments, using SQLAlchemy with Twisted
is practical now or not? Is it better to do it with Twisted than with
Gevent?
If you have the time to explain further about the persisting the session
comment
oh sorry. I thought the subject duplication shouldn't be in the mailing list.
I called configure_mappers() right before every query execution, but it does
not work still.
even one of erroneous class has only single column in table and has no foreign
keys or dynamical integration between any
oh, i fixed the problem. your explanation was exactly right. most of tables do
not seem to have any relation to errors so it was hard to find the error.
i have a dynamic module 'm' that is implemented to contain all ORM models for
convenience. one of relationship property referencing another
