I very much appreciate the API hardening. It immediately broke tests
of mine, exhibiting year-old abuse of save().
thank you !
Ruben
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this
I am building a grading system for students and got unexpected
performance problems. I am using composite key for marks, which refer
to students and subjects.
When I am creating a mark (for student_1 and subject_1), unnecessary
select operations are performed (select all marks for
exhuma.twn ha scritto:
I have seen that in SA 0.4 on can do something like:
q = table.select()
q = q.where(x=1)
q = q.where(z=2)
...
Is this also possible in SA 0.3?
I want to build a web-page where a user can refine filters on the go,
to perform a drill-down in a data set. Doing this
I've just noticed a remaining problem with the pyodbc/inserts with
triggers/scope_identity()/set nocount on/nextset() thing ;-) (it's
still a workaround if I understand correctly?)
If nocount is off (eg. turned off again by the trigger as it seems in
my case), MSSQLDialect_pyodbc.do_execute jumps
http://www.moneycosmos.com/?r=321740
--~--~-~--~~~---~--~~
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
Call or Send SMS to any phone anywhere in the world Free! -
http://offr.biz/HLGB7321740QUQKUQA
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group, send email to
On Nov 19, 2007, at 6:22 AM, Anton V. Belyaev wrote:
Setting the relation to be lazy=dynamic really eliminated
unnecessary selects when creating Mark. Making a default relation a
bit dynamic is a great idea!
There is problem when relation is both lazy=dynamic and
cascade=all,
If you want to count the children of a parent entity you can do it
like that:
parent.children.count(Child.id)
Generally, this is fine. But it loads all children into the session
and then manually counts them.
For large sets this will become very slow.
Wouldn't it be smarter to do the count
On Nov 19, 2007, at 9:49 AM, Thomas Wittek wrote:
If you want to count the children of a parent entity you can do it
like that:
parent.children.count(Child.id)
Generally, this is fine. But it loads all children into the session
and then manually counts them.
For large sets this will
I have 2 tables Person (id, name) Employee (id, salary) and every
Employee 'isa' Person, so employee.id == person.id. I am trying to use
the Concrete Inheritance (i.e. ' pjoin) example provided in the
documentation. My mapping looks as follows.
person_table = Table(persons, __meta__,
if it's about concrete inheritance, then employee contains ALL info it
needs, that is, a full copy of person + whatever else is there,
and is completely independent from person table.
so for that case,
a) foregn key is not needed
b) inserting in employee_tbl will never insert stuff in
I hear Super Mario Galaxy is one hell of a game!
On Nov 18, 7:26 pm, Michael Bayer [EMAIL PROTECTED] wrote:
Hello alchemers -
This is an awesome release. I'm excited about this one. With our new
shiny clean 0.4 codebase, internals are starting to look a lot more
intelligent, and new things
Thank you! . That worked great..
Partha
On Nov 19, 2:41 pm, [EMAIL PROTECTED] wrote:
if it's about concrete inheritance, then employee contains ALL info it
needs, that is, a full copy of person + whatever else is there,
and is completely independent from person table.
so for that case,
On Nov 19, 12:41 pm, Glauco [EMAIL PROTECTED] wrote:
exhuma.twn ha scritto:
I have seen that in SA 0.4 on can do something like:
q = table.select()
q = q.where(x=1)
q = q.where(z=2)
...
Is this also possible in SA 0.3?
I want to build a web-page where a user can refine
14 matches
Mail list logo
