On Sunday 29 January 2006 10:47, Ed Leafe wrote: > On Jan 28, 2006, at 2:36 PM, johnf wrote: > > What ever client program > > that is accessing the database - the login user must have the > > ability to > > "createDB" or create the database (and possiblely more). > > This is a general concern for all actions, not just table creation. > The login being used must have permission for update, insert and > delete for normal actions; if permissions are changed, an error will > be thrown when the framework tries to do one of these actions. > > Table creation, as well as table dropping, indexing and other sorts > of database setup and maintenance are not normally the province of > database applications; rather, it is usually the DBA or similar > administrator who performs these actions when the database is > initially set up, and occasionally thereafter to keep things running > smoothly and to accommodate changes to the business. > > So for this table creation, the framework is assuming that the user > has such rights, just as it assumes that the user has the rights to > insert, update and delete records. > > > -- Ed Leafe > -- http://leafe.com > -- http://dabodev.com
All true and the best way to handle dabo data access. An added note in the postgres case (and I gather other DBs too) just providing a user with createDB rights does not completely allow creation of all the required objects within the data engine. So attempting to setup a standard way to get this done does not seem likely to work. Therefore, I just provide a SQL script and allow the DBA to get it done. John _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
