Ted Pollari wrote:
> So, I guess if we're weighing in, I'd wish that SQLAlchemy would use a
> different term than 'session', but taking that as a given, I'd rather
> have Elixir use whatever nomenclature SQLAlchemy is, whenever it can.
I agree. I think the real issue is that SQLAlchemy uses a term that
is more commonly linked with web application development, which causes
confusion when SQLAlchemy is used for web application development. That
being said, the bottom line is that we're better off sticking with
SQLAlchemy's terminology wherever possible. We're making a push in
Elixir to make it clearer what is going on under the hood, and how we
relate to SQLAlchemy, and I think maintaining the same nomenclature as
SQLAlchemy wherever possible.
There is a built-in language function for this very situation:
from elixir import session as elixir_session
from pylons import session as pylons_session
I do agree that this is a frustrating namespace conflict, though.
--
Jonathan LaCour
http://cleverdevil.org
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"SQLElixir" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/sqlelixir?hl=en
-~----------~----~----~----~------~----~------~--~---
