Ο/Η Michael Bayer έγραψε:
django was not available to the public until it was fully functional
(youd go to the site and just get a coming soon-style splash
page)..and even then it was already in production use in earlier forms.
they knew that if you release something that wasnt polished and
after that post, ill never again doubt your trollish reputation.
--~--~-~--~~~---~--~~
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
closing off posting for this thread.
--~--~-~--~~~---~--~~
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
Ο/Η flyingfrog έγραψε:
Ok, this is my first approach with python + ORM, and i must say i can't
do what i want with it... Before that i used java Hibernate, think you
should know about.
Python fails in this discipline mainly due to:
* the lack of collaboration between projects (mainly
Ο/Η metaperl έγραψε:
TurboEntity was quite sweet. Supposedly a complete rewrite as a new
product is on its way though.
the first major problem of this rewrite:
it happens 'silently' (non-public)
.
--
http://case.lazaridis.com/wiki/Persist
django was not available to the public until it was fully functional
(youd go to the site and just get a coming soon-style splash
page)..and even then it was already in production use in earlier forms.
they knew that if you release something that wasnt polished and would
lead to user
SQLAlchemy lets you define separately DB code and python classes, but
then you hve a real duplication.
Duplication is bad, but you're never forced to duplicate
anything.Pythonoffers all the tools you need to prevent duplication,
and SA offers whatever
you need to 'extract' metadata from
On 12/16/06, Michael Bayer [EMAIL PROTECTED] wrote:
django was not available to the public until it was fully functional
(youd go to the site and just get a coming soon-style splash
page)..and even then it was already in production use in earlier forms.
they knew that if you release
yeah i know about the trollish reputation. the post that started this
thread was more or less a troll as well IMHO but everyone seems to be
responding to it anyway. but django's initial release strategy is on
my mind regardless...i have something else im hopefully releasing soon
but im
hibernate didn't magically appear, it was refined with input from users
over many years. if you want to help make sqlalchemy better for yours
and other usage. its much better to give concrete examples, that can be
used to improve it, then making grandiose negative statements. the idea
behind sa's
On 12/9/06, flyingfrog [EMAIL PROTECTED] wrote:
SQLAlchemy lets you define separately DB code and python classes, but
then you hve a real duplication. And to use database functionalities
you always need to access session objects or connections, making
sql-like queries. And i don't want that.
On 12/11/06, Michael Bayer [EMAIL PROTECTED] wrote:
Hibernate is pretty SQL oriented as well, and as I use it every day for
my job I can say it has little to nothing over SA...harder to
configure, more complex and less consistent behavior with regards to
relationships, poorer database support
Or get a day job at a company that uses nothing but sqlalchemy, like mine
:). Python coder resumes always accepted, especially from Mike.
-shoe
On 12/11/06, Kevin Dangoor [EMAIL PROTECTED] wrote:
On 12/11/06, Michael Bayer [EMAIL PROTECTED] wrote:
Hibernate is pretty SQL oriented as well,
13 matches
Mail list logo
