On 11/2/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > Jorge Godoy wrote: > .... > > > 'choose a Database Server you want to use with TurboGears' > > > (1.SQLite 2.MySQL 3.PostgreSQL) > > > > 4. None > > 5. what about other supported databases? If you're offering some help, why > > not helping everybody? > > > > Yes, I just toss some options, if we agree to do it, we can list more > and more...:-) > (or just give pysqlite, I'll explain latter) > > > Not every project uses a database server. I've put up one that just > > interfaces some characteristics from R to the web so that it can be used for > > educational purposes. :-) There are more coming. that is very true but we can still add None to the options. > > Right, but most of our tutorials need to use the model, unfortunately > new users try to learn turbogears with those tutorials :-) > > I'd suggest install pysqlite as default. Since our quickstart template > set the defaults for it, and py 2.5 already bundled it. With pysqlite > module installed, your first experience of Identity, tg-admin sql > create, ...etc won't cause scary exception messages. > The other benifit is that there's no need to configure sqlite server. > I don't think that's a good idea if someone comes to TG not knowing anything about their internals and they get a fully working sqlite install they may even think that TG uses that as db and never know you can upgrade. I have always been agains the default db to be uncommented, and I have seen some people get an error because went they add their dburi (and ConfigObj barks for having two values with the same key) because they don't even know the other is there.
> > > > In my humble opinion we shouldn't try selling the house if the person just > > wants to buy a new door. Giving guidance to where to find the modules and > > providing some help to where he can get more information to install these > > auxiliary tools. Otherwise we'd have to install the database servers > > themselves. > > > > I agree there too, TG is a framework not a canned app, if we add the db drivers then evantually someone will want to add install the db engine which is just wrong. > > I like the door metaphor :-) , if ORM is the door (Database is the > house), > customers may not feel uncomfortable that the door shipped without a > lock (database access module ex: pysqlite). > your missing the fact that people may choose mysql and you will give them the connector but then it will fail went no mysql server is present. > It's true they can live well without lock, > but some of them may feel they are cheated if they can't lock their > door.(without database access module, ORM is not functional) > again I think this should be added to the SO and/or SA package directly and not to TG. something like easy_install SQLObject[mysql] and so on. > The bad experience is that you buy the TV home and then you found > there's no remote. > The clerk told you you should choose one and buy it separately. It's > not 'battery included'. > I agree you have to be batteries included but we need to learn not to go too far. this is a flexible framework maintaining code for all the possible combinations is a pain and the one of the purposes of the ORM is for you NOT to worry about the db backend. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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/turbogears-trunk -~----------~----~----~----~------~----~------~--~---
