> -----Original Message-----
> From: Jean-Eric Cuendet [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 19, 2004 8:07 AM
> To: [EMAIL PROTECTED]
> Subject: [sqlite] SQL engine on our file formats
>
>
> Hi,
> We have our own files containing data for our automatic
> testing line. We
> would be interested to serve these informations through SQL. One idea
> would be to put them in an SQL database but we would like to
> stick with
> our text only files: easy to manage, to edit, to version.
If you are wedded to the text files, then the only options I can see are:
1) Re-import the text files into an sqlite database (in the background) when ever the
times stamps of the text files have changed - a poor mans replication, its not really
a good idea if the data set is large.
2) Don't use sqlite, use something else. Options off the top of my head:
shsql - http://midriff.sourceforge.net/sqlman/html/Contents.html
Perl DBI modules that can use text files via SQL (there is at least on CSV
based one)
ODBC driver similar to perl DBI modules that access text files via SQL
interface (I've not seen any ODBC drivers that do this under Linux, I've only seen
these under win32).
JDBC of the same form.
Chris
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
