On Jul 5, 10:52 am, "Rick Morrison" <[EMAIL PROTECTED]> wrote:
> 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?
Query.scalar() goes away, result.scalar() stays since yes, "scalar" is
the best word there (first column of first row).
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
