> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Wouter Heijke > > I was quite surprised to read the recent post about the > Applications 1 Full Backup export extension because i have > been working on the same issue. My basic approach was > similar, a full backup and ignoring the builders whose > content will be created by MMBase on startup. The difference > is that I use JDBC to connect to the database and read the > datamodel and all tables and fields, so currently i'm not > using any MMBase code, other then mmbase.util.Encode to > encode content.
Is this just a database backup facility or does it export to a MMBase application? Furthermore, using just JDBC to connect to the database, you'll have reimplement funtionality that's already present in the MMBase API's. That means duplicating functionality and a possible maintanance nightmare in the future. What's the point? Rob van Maris Technical Consultant Quantiq xmedia & communication solutions Koninginneweg 11-13 1217 KP Hilversum T +31 (0)356257211 M +31 (0)651444006 E [EMAIL PROTECTED]
