Hello,
Well, thank you for that. It's exactly what I needed.
The funny thing here is that I've been working on developping
approximately the same code for the past two or three weeks, with
exactly the same syntax... And I was about to announce it in a few
days (after cleaning it up and
That's very good news, maybe we can pull together the
best pieces of both approaches? I'd really like to see
your solution.
Daniel
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this
I'll send you a copy as soon as the basics work. For now, the system
is in place but only ManyToOne work. I wanted to also implement the 3
possible types of inheritance before publishing my code, but well, now
the circumstances are different... I'd be very glad if we could mix
both code bases.
wow this looks very nice. My impression is that its a lot more
reflective of SQLObject's specific API, is this accurate ?
On Oct 30, 2006, at 1:27 PM, Daniel Haus wrote:
TurboEntity is a high-level declarative layer on top of SQLAlchemy,
inspired by - but somewhat thicker than - Jonathan
Michael Bayer wrote:
wow this looks very nice. My impression is that its a lot more
reflective of SQLObject's specific API, is this accurate ?
Also, FYI, Daniel and I are already talking a bit about working with
each other. ActiveMapper and TurboEntity are very close in spirit, and
even
I've seen some other TG-named stuff (Turbo(Mail|Setup)) that only looks
to work with TG, so some people might assume that about your project as
well (if they're lazy and don't read).
I think the turbo prefix may not always mean that it's intended for
use with TurboGears.
Turbogears is
Right, TGWidgets. I wasn't suggesting it would cause mass confusion
or anything, just that since it's its own thing, being under the TG
namespace makes it look related to TG as opposed to a something that
works well with TG but just as well without.
Yep. Makes sense. I just noticed that
