I agree as well. We are upgrading a large, old application originally written almost 20 years ago. The additional time necessary for the most elegant solution can be very expensive. PCs today are powerful and cheap. The end user does not care if there is another layer inside, he only wants the application to work. Some of our customers are very small where SQLite, with its one database file and no administration required, is perfect. Many customers will insist that we connect to their corporate database servers. Robert's wrapper should make this possible with minimal fuss.
Don ----- Original Message ----- From: "Samuel R. Neff" <[EMAIL PROTECTED]> To: <sqlite-users@sqlite.org> Sent: Tuesday, May 29, 2007 11:06 AM Subject: RE: [sqlite] Re: CAST Actually I'd say he gave a great explanation of why the wrapper approach is so important. Robert went through all the work to make SQLite perform in a scenario compatible with many other databases so now the users of his wrapper don't have to. Saying not to use wrappers when programming in straight C and using only SQLite is one thing, but of course when developing in any other language or when supporting multiple databases wrappers are essential (all of our applications are in .NET and some support both SQLite and MSSQL). We would never have considered using SQLite for our product if it wasn't for Robert's SQLite.NET wrapper. Sam ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
