Hi, Thanks for the feedback but I was not thinking about network connections to the database. I was more think of ways to get an SQLite Database connected to every day database objects and controls. Most of todays database tools use ODBC. One typical example is how can I (easily) use SQLite inside VB for Databinding? If ODBC was standard then that would be a breeze not only for VB but for the hundreds for Rapid Application Development (RAD) software and components that are available today. __ Raymond Irving
Mitchell Vincent <[EMAIL PROTECTED]> wrote: Well put, Darren. Raymond, I would say that if you need ODBC then you need to use a different database (server) all together. SQLite fills the embedded database niche perfectly but it is not a replacement for MS-SQL, MySQl, PostgreSQl, Oracle or other database *servers*. If you need a RDBMS server you are better off using one instead of faking it with SQlite. PostgreSQL and MySQL both run on Windows and are free (well, PostgreSQL is free but who knows about MySQL these days.) Best of luck! Darren Duncan wrote: > At 7:25 AM -0700 5/17/04, Raymond Irving wrote: > >> I think SQLite should come standard with an odbc driver since ODBC is >> an "open standard" > > > I disagree. > > Partly this is because D. Richard Hipp would then have to start > certifying it like his own code and ensuring that it is always up to > date with the core SQLite code, since they would get released together. > That may be more responsibility than he wants. > > Second, SQLite was intended first and foremost for embedding, and for > the large fraction of people that use it that way, a database networking > layer like ODBC is not going to be used anyway. (That said, if SQLite > was intended primarily for a client/server use, then I would more likely > agree with you.) > > The networking code would significantly increase the size of the core > distribution, as well as make it harder to test, as networks have a lot > more variables to be concerned with than a local disk-based system does. > > By keeping the ODBC driver separate, those other people who see that as > their specialty can focus on it on their own time table. Let each > person focus on what they do best, and all that. > > Finally, while ODBC is very common, it isn't the only protocol for > networking databases, and some people may prefer an alternative. > > -- Darren Duncan > > --------------------------------------------------------------------- > 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]
