more.groupware

Hi!

On Do, Apr 29, 2004 at 02:57:45 +0200, Franky wrote:
> have you had any chance of re-adding the code to be able to add "sample 
> data" to te daabase again?

I know I promised, but I haven't added this yet. At least I know why
it has been removed from setup! :)

As we don't select what to install during setup any longer, it makes
no sense there.

So this should be added to the module manager. To be able to provide
sample data for core/base modules, which get installed during setup
this could
 a) be added to setup anyway
 b) be added to install.sql, update_*.php or even definition2.xml

None of those make me happy. So what about this:
 - Every module can have sample.sql files (and localized variants)
 - If file has sample data, there is a install link in the module
   manager

This allows an admin to install sample data at will, for all modules,
anytime.

This adds one caveat: sequences. If sample data is installed, but
sequences start at 1, duplicates *will* happen. One way around this
would be to start sequences for user data at, say, 100. Everything
below is sample data *only* (and could thus be removed againe easily).

Or we dump sequences, and use AUTO in the definition2.xml. Before we
do this, we must check where this works (I know it does on MySQL and
PostgreSQL, but on other DBs?). Removing sample data wouldn't be that
easy then, though.

Karsten
-- 
Karsten Dambekalns     k.dambekalns@...

http://www.k-fish.de/more_groupware.24.0.html
http://www.fishfarm.de/
-----------------------------------------------

Karsten Dambekalns wrote:

> None of those make me happy. So what about this:
>  - Every module can have sample.sql files (and localized variants)
>  - If file has sample data, there is a install link in the module
>    manager
> 
> This allows an admin to install sample data at will, for all modules,
> anytime.
> 
> This adds one caveat: sequences. If sample data is installed, but
> sequences start at 1, duplicates *will* happen. One way around this
> would be to start sequences for user data at, say, 100. Everything
> below is sample data *only* (and could thus be removed againe easily).
> 
> Or we dump sequences, and use AUTO in the definition2.xml. Before we
> do this, we must check where this works (I know it does on MySQL and
> PostgreSQL, but on other DBs?). Removing sample data wouldn't be that
> easy then, though.
> 

Or even a better solution for sample data: add the sequences used to the 
sample sql file as well ...
The issue is: if you do it with a link, you'll have to check wether or 
not the sample data has already been installed (you don't want to instal 
it twice)

Franky

Hi,

On Do, Apr 29, 2004 at 08:14:20 +0200, Franky wrote:
> Or even a better solution for sample data: add the sequences used to the 
> sample sql file as well ...

*This* breaks things if there is 'real' data already...

> The issue is: if you do it with a link, you'll have to check wether or 
> not the sample data has already been installed (you don't want to instal 
> it twice)

Well, one could delete the sample data before installing it. This
would allow to install sample data again, if you screwed it up while
playing around :)

Karsten
-- 
Karsten Dambekalns     k.dambekalns@...

http://www.k-fish.de/more_groupware.24.0.html
http://www.fishfarm.de/
-----------------------------------------------

Karsten Dambekalns wrote:
> Hi,
> 
> On Do, Apr 29, 2004 at 08:14:20 +0200, Franky wrote:
> 
>>Or even a better solution for sample data: add the sequences used to the 
>>sample sql file as well ...
> 
> 
> *This* breaks things if there is 'real' data already...
> 
> 
>>The issue is: if you do it with a link, you'll have to check wether or 
>>not the sample data has already been installed (you don't want to instal 
>>it twice)
> 
> 
> Well, one could delete the sample data before installing it. This
> would allow to install sample data again, if you screwed it up while
> playing around :)

Well, deleting sample data is not always that simple (I'm thinkng about 
the inventory module db structure).
So maybe it's best that, at the end of installation of a module, there's 
a link/popup to install the sample data (or maybe a link to install the 
sample data, and a popup to warn people that they can install sample data).
So you can only install sample data after you've just installed a 
module. Not twice, and we're sure there's no data in the module's used 
sequence tables as well.

Franky