Re^3: Database Web interface

In general, you shouldn't need to set up your classes for Class::DBI and Maypole more than once. Class::DBI::Loader should read your database configuration out of the DB, or you should manually tell Class::DBI what to do. Maypole can be coaxed to avoid Class::DBI::Loader and then you can give it your existing Class::DBI setup.

Of course you will still have to declare which tables are to be shown to the user, but that needs to be done anyway. Maybe you can fix that with some namespace walking magic, if you aren't using Class::DBI::Loader and want to export all classes/tables directly.

Comment on Re^3: Database Web interface

Replies are listed 'Best First'.
Re^4: Database Web interface by monkey_boy (Priest) on Sep 30, 2004 at 10:52 UTC
Again, thanks for the quick response, or you should manually tell Class::DBI what to do Can you point me to any examples of this? Is there a BeerDB example that im missing! Cheers! I should really do something about this apathy ... but i just cant be bothered	[reply]
Re^5: Database Web interface by Corion (Patriarch) on Sep 30, 2004 at 11:00 UTC
The documentation on how to tell Class::DBI what to do is in the documentation for Class::DBI. Because Maypole ties in closely with Class::DBI, a good knowledge of Class::DBI is necessary for using Maypole, at least that's my opinion on the things. You should read the documentation of Class::DBI and maybe look around on the Class::DBI wiki and mailing list to get a feel for the problems people have with Class::DBI. Then you can move on towards Maypole, but I recommend you start out with a supported database implementation, like DBD::SQLite.	[reply]