#Sql lite database for mac mac os x
#Sql lite database for mac code

This worked but I was puzzled to fnd that various functions were disabled although I knew they worked in the Sqlite source i was using (2.8.9). This failed at first, because a few source files have been added to Sqlite since the wrapper was last updated, so I added them in. Windows doesn't have GNU autoconf or automake, so Christian Werner supplies a makefile for Visual C++. The first problem I had came about when building the JNI library on Windows. Obviously it may fail if the Sqlite API changes, but so far all is good. You simply put the latest (or your preferred) Sqlite source in a subdirectory of his source, or specify the location of the source with an argument, and his JNI project will use that source. Christian Werner's configure script allows for this nicely. This makes them forks, albeit usually of a very minor kind, and you have the inherent fork problem of what to do when the main branch is updated.

#Sql lite database for mac code

Now, one of the problems with Sqlite wrappers is that many of them either include or modify the Sqlite code itself. It's a good project, and works exactly as expected on Linux: When it comes to Java, there is only one that I know of, and it is here. Fortunately many of the wrappers are themselves very small, so there is not too much to go wrong and you should be able to fix problems that arise. 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.

#Sql lite database for mac mac os x

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.