im more in favor of "Datasource", less so for Catalog.  i still think  
"Catalog" is vague, MetaData is a well known word and we can just  
describe it really carefully as "MetaData is a catalog of  
tables.....".   if you read fowlers book it *is* exactly what we are  
using it as, its information about your tables and columns stored  
programmatically.   i dont think people are walking away from SA  
because the word "MetaData" is too imposing, its how its combined  
with 5 other concepts that arent presented cleanly enough that would  
cause that to happen.

I think there are a lot of things about the docs that do chase users  
away, probably the biggest is the two separate worlds of SQL  
expressions and Query objects.



On Jul 27, 2007, at 2:26 PM, jason kirtland wrote:

>
> svilen wrote:
>> Anyway it may depend which audience are u targeting with these
>> names -  those who never seen an API or those for which names are
>> important  only to associate them with a
>> library/version/use-case... both  extremes are equaly
>> uninteresting imo.
>
> I came around to thinking about these names by looking at the
> tutorial, presenting and being presented to.  The engine and
> metadata have the honor of being the first things that anyone
> evaluating SQLAlchemy is exposed to.  Right after that, it's all
> tables, columns, results, and similar familiar territory.
>
> So the audience I had in mind is really everyone new to the
> project, at any level- a nebulous target, and more marketing than
> technical.  My thinking (which is not all that sophisticated on
> this) is simply, "Is there a pain point here for first-timers?
> Would a tweak increase adoption?"  It's also influenced a bit by my
> own experience, I recall hitting a little speed bump there myself.
>
>
> >


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" 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/sqlalchemy?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to