Re: How to package a database (not program)?
On Thu, Dec 11, 2003 at 09:47:45PM -0800, David Braun wrote:
> On Thu, 2003-12-11 at 12:42, Matt Zimmerman wrote:
> > I would simply include the SQL dump under /usr/share and leave it to the
> > user where to import it. It's possible that they will want to create a new
> > database, or import it into an existing one (perhaps even with different
> > table names), or transform it from SQL into something else.
>
> Thanks for the advice. Since sending my original message I've
> discovered SQLite and think it's the most appropriate database for my
> application (and probably for anyone else's application). SQLite stores
> its data in a file and doesn't use a server so it simplifies the problem
> significantly--all my package has to do is provide the file (under
> /usr/share as you suggest). There is value in my providing an SQLite
> file instead of what one gets from the USDA because they describe their
> tables in a PDF document, and it's nontrivial to type in the table
> description for the import process.
>
> If in the future someone has a need that goes beyond an SQLite file I'll
> be happy to package it differently, but I think this should be fine for
> now.
What if I want to import the data into a MySQL database? Is it trivial to
do that from an SQLite data file? If not, I think it would be a good idea
to provide the master format as well (SQL? tab-delimited?).
--
- mdz
Reply to: