Arnar Birgisson wrote:
> On 6/13/06, Lele Gaifax <[EMAIL PROTECTED]> wrote:
>> As said above, I'd use a different name for it,
>> though, as I find "Function" a bit misleading. Isn't ParametricTable a
>> better choice?
>
> Or perhaps "Procedure" since the sql syntax is "create procedure" vs.
> "create table"?
Yes, but I think it's misleading as well, since usually with "procedure"
you don't think at something returning data. But I agree it has the
advantage of being closer to a known concept.
BTW, I wonder *why* SQL engineers failed to expose the functionality in
a better way: couldn't a SQL engine easily consider the following
SELECT a,b,c FROM selectable_procedure(:x, :y, :z)
exactly equivalent to
SELECT a,b,c FROM selectable_procedure
WHERE param_x = :x
AND param_y = :y
AND param_z = :z
effectively hiding the fact that "selectable_procedure" is an SP instead
of a traditional table?
> ps. Lele, sorry for the double (or triple) post to you, I forgot to do
> "reply to all" <:-P
Don't worry. I usually strip all addresses except the ML one, when
answering to msg coming from a ML to avoid duplicates, but nowadays, who
care? :-)
ciao, lele.
_______________________________________________
Sqlalchemy-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
