But scalar() is useful on the SQL-API side for getting real scalar values like count(*) and etc. In this role, it functions as one would expect scalar() to do, getting a scalar value instead of a result set.
...or is it just the badly-named Query.scalar() that will be going away? On 7/4/07, Michael Bayer <[EMAIL PROTECTED]> wrote: > > > > > On Jul 4, 7:30 pm, Jose Galvez <[EMAIL PROTECTED]> wrote: > > Thanks Michael, > > I went back and reread the "Proposal" thread and I finally get what > > scalar() does and how it is different form one(). but how would first() > > differ from scalar() and how would all() differ from list()? At first > > blush they look like they would return the same type of query object > > Jose > > list() and scalar() get deprecated and go away in 0.5. > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
