The sample database contains lots of attachments, unused pages, etc. I would like to be able to set up an xwiki installation with a clean starting point; ultimately I will need to have my own SQL file to create multiple virtual xwikis each with the same custom initial state. In other words, it is not practical for me to manually remove and replace the sample content. Due to version history each virtual xwiki would be bloated with all the photos and other sample data. Has anyone created a minimal database SQL file? I assume it is needed as I did try running xwiki with an empty database. If not, any suggestions? Is there a good Hibernate tool that would make it easier to manually edit the database? (I tried editing the SQL but it is hard to separate the essential xwiki structure from the sample data.) Or is there some way to strip all the unused data from the database? -Trevor
Trevor, I haven't attempted to re-do this in about five months, so I can't send you a nice clean 'seed-data' load script, but I can offer some help. In the 'set-up' script that was shipping a couple of releases ago, it turned out there were really fewer than 50 insert statements. By taking the time to write down the 'synthetic keys' that are used for referential integrity, you can decipher what 'subordinate' table rows should be deleted when you delete a row from a 'major' table. In that way, you can get a pretty clean initial database -- one that will allow XWiki to start up without most of the extraneous content.. I am sure there are changes in the schema from what I did 'back then', but the general approach should still be valid. Sorry, I have not had time to update the actual process to coincide with the most current schema and sample database, but scanning through the attached still might be of some help to you. ----- Original Message ----- From: "Trevor Cox" <[email protected]> To: <[email protected]> Sent: Wednesday, May 25, 2005 22:05 Subject: [xwiki-users] Must I use the sample database?
The sample database contains lots of attachments, unused pages, etc. I would like to be able to set up an xwiki installation with a clean starting point; ultimately I will need to have my own SQL file to create multiple virtual xwikis each with the same custom initial state. In other words, it is not practical for me to manually remove and replace the sample content. Due to version history each virtual xwiki would be bloated with all the photos and other sample data.
Has anyone created a minimal database SQL file? I assume it is needed as I did try running xwiki with an empty database.
If not, any suggestions? Is there a good Hibernate tool that would make it easier to manually edit the database? (I tried editing the SQL but it is hard to separate the essential xwiki structure from the sample data.) Or is there some way to strip all the unused data from the database?
-Trevor
---------------------------------------------------------------------------- ----
-- You receive this message as a subscriber of the [email protected]
mailing list.
To unsubscribe: mailto:[email protected] For general help: mailto:[email protected]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
participants (2)
-
tcorbet -
Trevor Cox