I have a query that started to fail with r2620. Here is a portion on
the code and the exception that was thrown. I've tested against the
most current revision and that also fails. Is this something I'm
doing wrong or a real bug? --Thanks, Paul
in_sql =
Before opening a ticket I wanted to open a discussion on ways of
avoiding the MySQL connection timeout scenario (a symptom of this is
the MySQL server has gone away exception.)
=Background for those interested=
MySQL enforces an idle connection timeout policy. Additionaly, the
connection protocl
howdy.
here the use case.
i have object Parent, which has relation to many objects Child.
so, in UI, i have dialog editor for the Parent object, which has some
direct attributes (name, age, etc), and some list of Children.
Adding a Child to the list, or editing attributes of existing child,
is
Isn't this the very thing that the session / UOW constructs are supposed to
address for case #1?
This can all break in a web application that doesn't want to maintain any
in-memory state at all -- for those you can serialize via
pickle/JSON/whatever the objects being manipulated and hold them in
thats a use case that didnt get tested when i committed 2620, try 2640.
On May 23, 2007, at 2:12 AM, Paul Kippes wrote:
I have a query that started to fail with r2620. Here is a portion on
the code and the exception that was thrown. I've tested against the
most current revision and that
On May 23, 2007, at 10:44 AM, Aaron Iles wrote:
=Discussion=
1. Is this an issue that SQLAlchemy ought to be concerned with. Or is
this an issue for the utilising applicaiton?
SQLAlchemy is concerned with this.
=Possible Solutions=
There are at least two possible solutions inside of
On Wednesday 23 May 2007 18:18:42 Rick Morrison wrote:
Isn't this the very thing that the session / UOW constructs are
supposed to address for case #1?
This can all break in a web application that doesn't want to
maintain any in-memory state at all -- for those you can serialize
via
David Leuschner wrote:
this is a bug that was introduced in r2556, where an optimization to
the SQL used to query the remote table was not properly accounting
for a many-to-many join criterion, fixed in rev 2625.
Thanks for the fast response! I've just found the new entry in the
Changelog and
Michael Bayer wrote:
I should learn to explain better what syncrules are about, so heres
an attempt:
when you have a table A and a table B, and then a mapping relationship
between A and B, theres a join condition set up between the two tables.
By default, it draws from the foreign keys of
Responding to myself. As I wrote the first message, I started thinking
how just deleting the FK after metadata.create_all() wouldn't be so bad
and now I think that's a pretty good solution.
Randall
Randall Smith wrote:
Michael Bayer wrote:
I should learn to explain better what syncrules
This is the error: Note that the first param is an SA object instead of
the integer key.
sqlalchemy.exceptions.SQLError: (ProgrammingError) can't adapt 'SELECT
records_tinwsys.tinwsys_st_code AS records_tinwsys_tinwsys_st_code,
records_tinwsys.tinwsys_is_number AS
Never mind. My mistake. --Randall
Randall Smith wrote:
This is the error: Note that the first param is an SA object instead of
the integer key.
sqlalchemy.exceptions.SQLError: (ProgrammingError) can't adapt 'SELECT
records_tinwsys.tinwsys_st_code AS records_tinwsys_tinwsys_st_code,
With this relationship
Record.mapper = sa.mapper(Record, records,
properties={
'tinwsys' : sa.relation(Tinwsys, secondary=records_tinwsys,
backref=sa.backref('efile_records')
}
)
SA is deleting associated records in records_tinwsys when a
On May 23, 2007, at 4:15 PM, Randall Smith wrote:
With this relationship
Record.mapper = sa.mapper(Record, records,
properties={
'tinwsys' : sa.relation(Tinwsys, secondary=records_tinwsys,
backref=sa.backref('efile_records')
}
)
SA
On May 22, 12:29 pm, [EMAIL PROTECTED] wrote:
On May 22, 2007, at 2:12 PM, [EMAIL PROTECTED] wrote:
I have a transaction that uses save_or_update() and takes 2-3 minutes
to execute:
There's some setup before the transaction (pseudocode for brevity)
contact = Contact()
# ...set
Hello list,
I am a newbie to sqlalchemy and have been playing around with it in a
windows environment w/ mssql.
I keep getting this error after I do an insert. The insert is
successful, but I think there is a problem in getting the pk
afterward.
Thank you very much,
Jin Lee
import pyodbc as
Hi Jim,
The autoload feature for SQLAlchemy sometimes guesses wrong about
auto-sequenced columns. Check that your users.user_id column has an
auto-generating key (IOW, is it of type IDENTITY)?
If so, please post your version of MSSQL and pyodbc. IDENTITY insert for
MSSQL columns has recently
On May 23, 2007, at 5:46 PM, [EMAIL PROTECTED] wrote:
Just to follow up on the issueI was able to trace the momentary
deadlock to a call to
user.groups.append(Group.get_by(group_name='somegroup')) during the
setup of new contact.user.
oh and what happens then, the backref on Group lazy
18 matches
Mail list logo
