On Mon, Jul 21, 2008 at 5:22 PM, Walter Cruz <[EMAIL PROTECTED]> wrote:
>
> Using SQLAlchemy 0.5 and elixir 0.6, with pylons:
>
>>> dir(model.Page
> ... )
> ['__class__', '__delattr__', '__dict__', '__doc__',
> '__elixir_mutators__', '__getattribute__', '__hash__', '__init__',
> '__metaclass__', '__module__', '__new__', '__reduce__',
> '__reduce_ex__', '__repr__', '__setattr__', '__str__', '__weakref__',
> '_descriptor', '_global_session', '_sa_class_manager', '_setup_done',
> 'allparents', 'changed_at', 'children', 'created_at', 'delete',
> 'expire', 'expunge', 'flush', 'from_dict', 'get', 'get_by', 'id',
> 'lastDate', 'mapper', 'merge', 'parent_id', 'refresh', 'save',
> 'save_or_update', 'set', 'slug', 'table', 'text', 'title', 'to_dict',
> 'update', 'update_or_create']
>>>> model.Page.query
> Traceback (most recent call last):
>  File "<console>", line 1, in <module>
> AttributeError: type object 'Page' has no attribute 'query'

As I said on IRC (but I didn't get your answer), that's kinda strange
because the only case I can see where the query attribute would
disappear in a 0.5.2 to 0.6.0 Elixir upgrade would be if you were
using a SessionContext which was already deprecated in SA 0.4.1 and is
not even present in SA 0.5.0...

The only other case where you don't have a query attribute is if you
use a manual session (ie using_options(session=None) or __session__ =
None), but this is by design (since it doesn't make sense to have a
.query attribute in that case).

If that doesn't solve your problem, please file a bug in our trac with
a short *but runnable* example demonstrating your problem.

Hope it helps,
-- 
Gaƫtan de Menten
http://openhex.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
-~----------~----~----~----~------~----~------~--~---

Reply via email to