Hey Maurice, 2010/1/18 Maurice Gittens <[email protected]>: >> Yes we need that. But we need ideas to keep this simple too. >> > > Is Wt::Dbo intended for the problem space where the programmer controls the > database? Or is it > intended as a general purpose RDBMS manipulation and access interface.
It is intended for the problem space where the programmer controls the database. > The fact that Wt::Dbo automatically does schema creation entails > that it includes schema and schema object creation policy. > > - Could you spell out the Wt::Dbo policy for database management is? Wt::Dbo was created for the case of a typical web application. All data is accessed through a single database user. Most (if not all) database access is through Wt::Dbo. You can let Wt::Dbo create a schema for you (which is mostly a convenience during development), or you can manage the schema yourself (which is what you will end up doing during deployment). You are not obliged to use schema creation of Wt::Dbo, and as such I would not consider that Wt::Dbo has a policy there. The term 'database management' is quite generic and overloaded; what exactly do you refer to ? > - Should database constraints now be handled by Wt::Dbo? "Should" implies that there is a reason for it: no. But if you use Wt::Dbo to create the schema, it will obviously add some constraints for you. > - Should database access control be handled through Wt::Dbo? It should be handled through the application that uses Wt::Dbo. > - Triggers & stored procedures anyone? You are free to manage your own triggers and stored procedures. The idea is that you use Wt::Dbo for simple CRUD and queries (including relationship traversal) and serialization from database records to C++ (composite) data types. > - Is it appropriate for the DBA to manipulate the Wt:::Dbo database schema > objects without using Wt::Dbo? For sure. > I fair that Wt::Dbo is a way for Emweb to make other peoples mistakes (see > this thread for example), So I found out that there are two categories of programmers when you involve a database. Some people believe that ORMs are silly because they create additional problems and do not solve any. They believe that you should use all the bells and whistles of your database and not be restricted by any layer in between. Then there are other people (I guess like me) who have developed several applications using Hibernate or an other ORM tool and were pleased to be able to conveniently manipulate the database from within his object oriented language, and were also pleased they could tell their customer to deploy using the database that they feel most comfortable with. > all over again. All to the detriment of the still not finished core Wt > functionality. I think this is not a fair judgement. Wt::Dbo is less than 5% of the code base of Wt, and far less development effort. Even during the (brief) period that we actively developed Wt::Dbo, we did more improvements to Wt itself. > Maurice 'wishing Wt would do one thing and do it well' Gittens I also wish Wt could do one thing and do it well. But it seems that our users cannot agree on the one thing, and looking at the applications that people develop with Wt, there is a diversity that I would never have predicted beforehand. And I am happy to see that, but it means that yes we still need to work hard on improving Wt and extending it in all directions and there are more directions than we originally anticipated. But perhaps you should just indicate of what is on your wishlist instead of saying what isn't. Regards, koen ------------------------------------------------------------------------------ Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
