[sqlalchemy] Re: ORDER_BY always in SELECT statements?

2007-10-01 Thread Michael Bayer


On Oct 1, 2007, at 8:20 AM, [EMAIL PROTECTED] wrote:


 Hi Michael, thanks for the help!

 The documentation mentions that this option over-rides the per-engine
 configuration but I couldn't find a create_engine option to set this.
 Any reference would be greatly appreciated!


uhhh there is no per-engine configuration of ORDER BY, those must be  
some old docs youre reading.  ORDER BY is only defaulted in the ORM  
at the mapper() and relation() level.

--~--~-~--~~~---~--~~
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 PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sqlalchemy?hl=en
-~--~~~~--~~--~--~---



[sqlalchemy] Re: ORDER_BY always in SELECT statements?

2007-09-28 Thread Michael Bayer


On Sep 28, 2007, at 3:00 PM, [EMAIL PROTECTED] wrote:


 Hi,

 While trying to debug my script I set echo=True and checked the SQL
 statements that are generated. I noticed that all of the SELECTs
 issued to the DB have the ORDER_BY clause -- even though I didn't
 explicitly specify order_by() nor do I care about the order.

 Is this normal? Is there any way to turn this off?

im assuming youre talking about mappers.  specify order_by=None in  
the mapper() (and in relation()s) to turn off the default ordering.



--~--~-~--~~~---~--~~
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 PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sqlalchemy?hl=en
-~--~~~~--~~--~--~---