> If you need a special function foo() use the extension api of sqlite.
This is perfectly correct! Few bytes are the footprint of a quick and small database. Thats is more or less the definition. Code that is rarely used and also, does not provide a core function in sqlite, should simply not be there. The discussion gets off the target because if you ask someone if support for this function or that thing is compiled in, there will always be stuff missing and the design goal for sqlite will start diverge from the "small footprint trademark". However, first of all, I am an administrator, and a user and mainly uses and implements sqlite in my applications so bare with me if am totally off track here. My opinion is that the core code should be extremely small and fast and complie to ansi sql as far as possible. To this, the interface where you can add functions should be more of a public library where people needing a certain algorithm , say crypto or compatibility for this or that version, just should be a downloadable plugin. Just have a project that checks the contributed name standard of the provided functions so that it does not by accident can be found two plugin-functions with the same name. Ideally, someone is also reviewing the patches for qualtiy before they are put in the public plugin-area. regards, Jonas Forsman ----- Original Message ----- From: "Michael Roth" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, February 07, 2004 2:04 PM Subject: Re: [sqlite] OK to drop support for legacy file formats? > Rene wrote: > >>Why not remove the feature but create a seperate utility project that > >>converts any version of SQLITE DB to the latest version. > > > > > > i think it's better to let it in. why save a few bytes for removing such > > important functionality. by the way, same for md5, you should add support. > > You need MD5. The nextone needs SHA1. Another one needs CRC16. Some > folks may need a function to count hills in an given area. > > Sqlite is a database library and isn't an universal calculator. A > software package should do one thing and should it do well. A database > should store and retrieve data and shouldn't calculate crypto stuff. > > If you need a special function foo() use the extension api of sqlite. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
