> In the case of SQLite, I (arguably) have to use a 3rd party > management > tool, for which my custom functions are no longer available. I'm > curious how others handle this. > > A. You don't need or use any custom SQL functionality > B. You don't use a 3rd party SQLite management tool > C. Something else I haven't thought of?
I think that the key point you're missing here is that SQLite is not intended to be standalone database system like the other products you mentioned (Access, Oracle, etc.) - it is an embeddable database library. It happens to have a convenient command line interface that allows it to be used as a standalone database, but that's just a shell (pun intended) that allows you to get to the library itself. The 3rd party "front ends" to which you refer are really application consumers of SQLite itself - not add-ons to or features of SQLite. In other words: it's a development tool, not a database. Now, as for a "power" function: we had exactly the same need when we first started using SQLite. Our solution: we added it. The source code is freely available, after all. Adding a new function to the code is shockingly straightforward; from there you simply compile your version of the library and use that in your application(s). Quick, simple and portable, both across platforms and applications using your version of the library. -Tom ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
