If you want to back up only part of a database, you could consider doing mysqldump and listing explicitly the tables you want to include. You could put that into a script, which you maintain when you make changes to your schema. That way you could restore most of the tables easily, but plan to separately restore the other tables from the big text file if necessary.
On Jan 4, 2008, at 4:35 PM, Nicolai wrote: > Hi again, > > I kind of feel stupid now, but at least I learned a lesson. > > For some reason my database connection component did not throw an > error when it should have. A simple typo made it connect to a wrong > database, to which that user did not have access to. > > I simply left the problem alone for a while and returned to it seeing > the obvious mistake I made. > > Everything is working as expected - if my fat fingers would have type > the right name from start :( > > Sorry for troubling you all. But I wouldn't mind getting hints on how > to make database connections even better, still. > > Goodnight from Denmark > > Regards > > - Nicolai > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Mason-users mailing list Mason-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mason-users
