Re: [Sqlalchemy-users] first impressions

[Michael Bayer]

thanks, ill add that patch. ill look into those docs changes, still a long way to go on those.   ive been shooting for an end-to-end SQL toolkit and not just an ORM, even though I guess ORM is what most people are looking for...so I have tried to make the docs pretty open ended.  Since "Basic Data Mapping" does give an overview of the ORM without too many knowledge dependencies, maybe I can highlight that on the "Roadmap" page as something you can just look at quickly.  also, as far as naming "Roadmap", ill have to think of something...its meant as a summary as to what information you need to have in order to learn the next thing fully..i.e. the "direction-ness" of it is the most important thing, and I probably subconsiously got that name from the "Trails" or whatever they call them in the old Java tutorials. in other news, Oracle support has been kicked back up to current thanks to a new Oracle Express/Fedora installation which only took 8 hours to complete thanks to a broken CD burner, and will be checked in later tonight, and I am further refining the notion of "things you can SELECT from" / "things that make up the column list of a thing you can SELECT from" so that mapping against arbitrary SELECT statements, including those with functions and expressions inside of them, works across all databases. thanks all around, - mike On Dec 29, 2005, at 3:25 PM, Jonathan Ellis wrote: So far so good.  SqlAlchemy works as described and doesn't crap out cryptically when I try to do something unexpected, unlike some other ORM tools...   Here's some thoughts while I'm still thinking like a newbie. SqlAlchemy's autoload was crapping out on "timestamp with timezone."  I added this to postgres.py (patch attached). Nothing I ran across has __repr__ defined which makes REPL a pita, having to dir everything... Some comments on the docs:   Most projects use the term "Roadmap" to denote planned features.  Perhaps "sqlalchemy concepts" or "Under the hood" would be less confusing.  It would be nice to have a Quickstart section come before this section, too; right now the first impression a newcomer to SqlAlchemy has is probably "Holy crap!  This is WAY more complicated than SqlObject!"  Basic Data Mapping is pretty close to this already, I think. Establishing a Database Engine: I'd suggest leaving out **opts from the examples since without examples of possible values it isn't useful except to tell people "this is more complicated than you need to know about at first."  Which they can probably guess anyway. :) -- Jonathan Ellis http://spyced.blogspot.com <ts-tz.patch>