On Sat, Oct 16, 2004 at 07:26:10PM -0400, sean finney wrote:
> applications. i'd greatly appreciate input, especially from the current
> maintainers of database-using or database-server applications. the draft
> is available at:
>
> http://people.debian.org/seanius/policy/dbapp-policy.html
[That should be http://people.debian.org/~seanius/policy/dbapp-policy.html,
BTW]
I'm missing some "Best practice" on how to setup the database itself. That
is, how to setup the tables (indexes, whatever...) that the application
will use from the database and, maybe, even some initial data in some of
the tables.
One common issue is that the application depends on that in order to work
and it's not done automatically. Maybe the user is prompted to do it but he
might be unable to do so until the installation is finished. For an example
of this problem see #205683 (and #219696, #265735, #265878).
It might be good to provide a common mechanism to setup the database so
that users are not asked to run an SQL script under /usr/share/XXX (usually
doc/package/examples). Maybe even defining a common location for these
(/usr/share/db-setup/PACKAGE/XXXX.{mysql,pgsql}?). Notice that the SQL
script that needs to be run might difer between RDBMS.
Just my 2c
Javier
Attachment:
signature.asc
Description: Digital signature