Hi, Jonathan and Remi Thank you so very much for your responses - I really appreciate it.
Remi, I haven't tried your approach yet, but will be playing with it a little later this evening. (Actually, I just tried it now, et voila!) I realise that "your" q and "Jonathan's" q must be related somehow - I'm sure I'll figure it out eventually. Jonathan, your second response work like a bomb, thanks. However, I did try your first proposed solution first, but iPython kept on complaining: type object 'Document' has no attribute 'q'. I realise that I'm missing something small here, like perhaps an additional import, and will scan through the SQLAlchemy tutorial again this evening to see if I can spot the problem. I think that part of the problem for me is the fact that example snippets in the various tutorials and reference pages are exactly that - snippets - so the infrastructure required to make the various examples work properly, when "thrown together" is not entirely clear to me. And, as I mentioned in my initial question, the interplay between Elixir and SQLAlchemy seems somewhat shrouded in mystery to me at this stage. What parts are catered for by the Elixir and which by SQLAlchemy? Obviously, Elixir (and that's also why I used it, having tried SQLObject a little before) takes care of the definition/ declaration of the objects and the database structure in a very neat end readable way. But one is certainly left with the idea that queries and selections can be tackled from Elixir too. I was rather hoping to keep things simple and, perhaps, do my thing mainly from the Elixir perspective (while my requirements are simple). But the "processing" power lies with SQLAlchemy, and I cannot quite figure out when I'm supposed to be "Elixiring" or "SQLachemying", or which imports need to be used at which level, or how much of the basic SQLAlchemy functionality is "inherited" by importing and using Elixir. (Sorry for this very long story - just trying to state my case as clearly as possible. Anyhow, I really enjoy Elixir, and found it fairly painless to get to grips with it, as far as the modelling is concerned. Thanks for an excellent "product" - not that I'm qualified to really comment. I shall persevere... --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
