On Jul 13, 2007, at 1:47 AM, Arun Kumar PG wrote:
Hi Guys,
I am getting this error when multiple requests are coming to the
application and following this the my server crashes!
FYI:
I am using MySQLDb library and connextions are managed by
sqlalchemy.pool
ProgrammingError: (2014,
Maybe actually asking some questions would have helped getting
replies :-)
Is this not a bug? I may be wrong, but I would consider this a pretty
serious bug, as it does not raise an error, but silently returns the
wrong object, which could lead to serious data corruption...
If it is, should I
On Jul 13, 2007, at 3:50 AM, [EMAIL PROTECTED] wrote:
i played a bit with your thing...
how do u expect the id column to appear in the Employee actualy?
do u expect to get the base person' one, or the child one? or both?
looking from the child, yes, the child one will obscure the parent
On Jul 13, 2007, at 2:27 AM, Arun Kumar PG wrote:
I create an orm session as soon as the request comes in and store
the reference to the same in the curent thread i.e.
threading.currentThread().session = new_session. This session is
stored in the current thread so that I can get the
Patch is attached again
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this group, send email to [EMAIL
On Jul 13, 2007, at 4:07 AM, Esceo wrote:
Hi all,
attached is an experimental patch for mssql.py merged with r2891:
this is a direct steal from the oracle implementation of limit +
offset using row_number()
what I would like to find out are the following:
the oracle implementation
Thank you for the extremely speedy response :)
Are we aware of any other impacts of oracle's offset+limit implication?
On 13/07/07, Michael Bayer [EMAIL PROTECTED] wrote:
On Jul 13, 2007, at 4:07 AM, Esceo wrote:
Hi all,
attached is an experimental patch for mssql.py merged with
i played a bit with your thing...
how do u expect the id column to appear in the Employee actualy?
do u expect to get the base person' one, or the child one? or both?
looking from the child, yes, the child one will obscure the parent
one, but from the parent.. u'll never get the child one.
i
On Jul 13, 2007, at 2:26 AM, Yves-Eric wrote:
Maybe actually asking some questions would have helped getting
replies :-)
sorry, i totally did not see this message on july 2 ?
Is this not a bug? I may be wrong, but I would consider this a pretty
serious bug, as it does not raise an
Hi all,
attached is an experimental patch for mssql.py merged with r2891:
this is a direct steal from the oracle implementation of limit +
offset using row_number()
what I would like to find out are the following:
the oracle implementation has visit_compound_select marked as todo,
what is the
Hi, I've been using SQLAlchemy since a month. I'm having some
problems with a one-to-many relationship. I have 2 tables: one for
users and one for users's emails. The problem arises when I want to
put a timestamp in the email table in order to see when a given
account was created. Here
Disclaimer: I'm no SQLAlchemy guru.
On Fri, Jul 13, 2007 at 01:53:48PM -, robertz23 wrote:
Hi, I've been using SQLAlchemy since a month. I'm having some
problems with a one-to-many relationship. I have 2 tables: one for
users and one for users's emails. The problem arises when I
also send along a full stack trace so at least it can be seen where
this is occuring.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group, send email to
On Jul 13, 2007, at 4:42 AM, Arun Kumar PG wrote:
Any thoughts?
my thoughts are, either the bug still remains in SA's connection pool
and everyone is magically avoiding the problem somehow (when it was
fixed, people who observed the problem all the time noted that it
went away
Thx Michael.
Well, I don't think that I am doing that. To give you a picture of the
object model this is how the hierarchy is:
BaseOrmDao (+GetSession() this returns the
session attached to the current thread)
^
|
Request -
i cant reproduce that on this end. created the tables, inserted a
row into each, script returns fine (note its using a long value, i
thought that might be an issue, but its not). make sure youre on the
latest MySQLDB driver. also not sure if an older MySQL might be
problematic as well
On Jul 13, 2007, at 4:20 AM, lei you wrote:
Thank you for the extremely speedy response :)
Are we aware of any other impacts of oracle's offset+limit
implication?
it has issues with DISTINCT as well. there is ticket #536 for this
which I spent some time with but not enough to
Sure Michael I will get back on this in a while as I am researching on this.
Thanks for your support. I hope this gets resolved sooner as I am very much
dependent on this and the application is really critical and should be up in
next couple days!
Thanks and i will get back on this in next couple
The latest trunk seems to have fixed this issue.
Thanks
On Jul 12, 6:22 pm, jason kirtland [EMAIL PROTECTED] wrote:
bbull wrote:
I have some code that returns what I'm calling a table object.
return getattr(self.dbc, tablename)
where self.dbc is an SqlSoup object and tablename is the
i played a bit with your thing...
how do u expect the id column to appear in the Employee actualy?
do u expect to get the base person' one, or the child one? or
both? looking from the child, yes, the child one will obscure the
parent one, but from the parent.. u'll never get the child
Thanks for the answers. I've tried what Christoph told, but returns
the same error. What I'm trying now is to override that column to be
a DateTime type because in this case SQLAlchemy doesn't give me any
errors, so I think you are right Michael, is because of the driver.
Can tell me how to
On Jul 13, 2007, at 3:41 PM, robertz23 wrote:
Thanks for the answers. I've tried what Christoph told, but returns
the same error. What I'm trying now is to override that column to be
a DateTime type because in this case SQLAlchemy doesn't give me any
errors, so I think you are right
22 matches
Mail list logo
