These range from finished code to various states of pre-alpha, alpha and beta. the main author), the same does not apply to all the wrappers out there. Note that while there's no doubting the qualiity of the Sqlite database library itself (kudos to D. I've also included some downloads for two things I found tricky - using the Mono Sqlite data provider with Microsoft.Net, and using the Java Sqlite wrapper on the Mac. What follows is a few notes on how I've got on so far. I was also interested in the possibility of porting the application to Java in order to run on Mac OS X and Linux, the two main "other" desktop platforms. I decided to investigate the feasibility of using Sqlite as an alternative to Microsoft's JET (the Access database engine) in a. Sqlite strikes me as nearly ideal for applications that need fast and robust access to local data. A SQL API is more portable, despite the dreaded implementation differences. So if you use the Codebase API and then later want to upscale to SQL Server or Oracle or DB2, everything will need to be redone. You can use SQL via its ODBC driver, but frankly ODBC should not be necessary for an embedded database.
The problem with Codebase is that it is at heart Xbase and not SQL.
It reminds me in some ways of Codebase, another excellent database library that runs everywhere. I like it because it is lightweight, fast, cross-platform, and supports a very decent subset of SQL.
0 kommentar(er)
