[sqlalchemy] Re: TurboEntity announcement
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 documenting it a bit)... I got a first working prototype yesterday. I've looked briefly at your code and it seems like we've taken drastically different approaches for exactly the same goal. Anyway, I'm too far in the process now to just let it go, so I'll just finish it as if I didn't know your project existed, then I'll look at what you did more thoroughly and either contribute to your project or try to convince you to switch to mine. ;-) PS: I hope I don't sound too frustrated here. Of course, I'm a bit frustrated not to have been the first here, but I am sincerely happy somebody did what I need. Greetings, Gaëtan. On 10/30/06, Daniel Haus [EMAIL PROTECTED] wrote: TurboEntity is a high-level declarative layer on top of SQLAlchemy, inspired by - but somewhat thicker than - Jonathan LaCour's ActiveMapper extension. Features currently include: - automatic polymorphic inheritance - easy specification of relationships - automatic creation of primary keys - automatic creation of foreign keys - automatic creation of secondary tables - relations can be specified across modules More information, documentation, examples and baloons for the kids can be found at http://turboentity.ematia.de/ And here's the blog post. Comments are open! http://www.danielhaus.de/2006/10/30/announcing-turboentity/ Please let me know what you think about TurboEntity and if you find it useful. Greetings, Daniel --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups sqlalchemy group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy -~--~~~~--~~--~--~---
[sqlalchemy] Re: TurboEntity announcement
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 group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy -~--~~~~--~~--~--~---
[sqlalchemy] Re: TurboEntity announcement
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. FYI, the main difference in my code is that I don't defer classes, I only defer fields, and create them as soon as what is needed for a particular field is defined. So I had to implement a very simple dependency system... It felt like a better approach but I'm not really sure about it... Gaëtan. On 11/1/06, Daniel Haus [EMAIL PROTECTED] wrote: 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 group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy -~--~~~~--~~--~--~---
[sqlalchemy] Re: TurboEntity announcement
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 LaCour's ActiveMapper extension. Features currently include: - automatic polymorphic inheritance - easy specification of relationships - automatic creation of primary keys - automatic creation of foreign keys - automatic creation of secondary tables - relations can be specified across modules More information, documentation, examples and baloons for the kids can be found at http://turboentity.ematia.de/ And here's the blog post. Comments are open! http://www.danielhaus.de/2006/10/30/announcing-turboentity/ Please let me know what you think about TurboEntity and if you find it useful. Greetings, Daniel --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups sqlalchemy group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy -~--~~~~--~~--~--~---
[sqlalchemy] Re: TurboEntity announcement
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 share some code. It would be nice if the two could have a shared future. I have even suggested replacing ActiveMapper with TurboEntity at some point down the road. TurboEntity certainly brings more documentation and a new contributor into the mix. I am very excited about the potential ahead! -- Jonathan LaCour http://cleverdevil.org --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups sqlalchemy group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy -~--~~~~--~~--~--~---
[sqlalchemy] Re: TurboEntity announcement
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 spinning off some core parts (widgets in particular) into framework independent libraries. And those may also have the Turbo prefix. But really I don't think the lack of a naming convention will create too much trouble. It is worth a mention on the TurboEntity site though! --Mark Ramm www.compoundthinking.com/blog --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups sqlalchemy group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy -~--~~~~--~~--~--~---
[sqlalchemy] Re: TurboEntity announcement
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 it's called TGWidgets because TurboWidgets is already taken, and it's NOT a TurboGears or even a Python related project. The namespace confusion is inescapable! -- Mark Ramm-Christensen email: mark at compoundthinking dot com blog: www.compoundthinking.com/blog --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups sqlalchemy group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy -~--~~~~--~~--~--~---