Dennis Cote <[EMAIL PROTECTED]> wrote: > > It could be any application that uses a fixed set of predetermined SQL > statements to perform its operations. My primary application does > exactly that using SQLite with all statements prepared and cached as > needed. It runs on a standard PC under Windows. We have no need for > executing arbitrary, runtime generated, or user supplied SQL as many > other applications do. Every SQL statement that can be executed is known > before the application starts. >
Your application uses a fixed set of SQL statements now. But that set of statements might change in the next release. Or you might change or modify a table, or add an index. A key feature SQLite is that these changes preserve the file format. With other systems, when you change the schema the file format changes with it. One of the ideas I try to push is SQLite as an Application File Format. The idea is that you put your information in an SQLite database file and it is then readable by diverse, general-purpose tools, and across multiple releases. Sure, the schema might change from one release to the next, but the data is still easily accessible. In order to promote this idea, we are very careful to make sure that the SQLite file format does not change in ways that are not backwards compatible. Our goal is to make sure that the information you put into an SQLite database today is still easily accessible using general-purpose tools after 20 or 30 years. Further to this goal, watch for detailed specficiations of the SQLite file format to appear in 2008. -- D. Richard Hipp <[EMAIL PROTECTED]> ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
