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 -~----------~----~----~----~------~----~------~--~---
