I was asked to write some words about the usage of the MSKSQLiteWrapper.
Well, actually I hoped, that most of the stuff can be read from the tests delivered with application “MSKSQLiteWrapperTests”, but additional documentation may not be that bad 🙂
Before starting with that library you should download the latest available library from www.sqlite.org. The downloaded library is about 500 KByte large and should be copied into the “bin”-directory of your VASmalltalk installation or running VASmalltalk application. That’s all !
GLORP, ABT and all other stuff …
With 8.02 an initial (old) version of GLORP is delivered with VASmalltalk. Therefore the whole idea about O/R mapping gets refreshed under our platform again. The VA-port of GLORP was written (back in those days at CampSmalltalk in Essen) against the database-interface of VASmalltalk (somewhere around VASmalltalk 5.5).
Therefore a database interface must be compatible with the VASmalltalk-database-interface to be useable with GLORP and additional code must be added/exchanged within the VADatabaseAccessor class. To my surprise some code for the MSKLSQLite wrapper has already been added to this class, but commented out.
Therefore out of the box the code will not work together with GLORP.
In addition to this the code in “GlorpDatabase” is not very extension-friendly (and packager friendly). In my opinion, references to DB2, Oracle, ODBC (on our platform) should be extracted to other applications and all those “Smalltalk at: Symbol” code should be rewritten …. what I am missing here is an information from Instantiations, how work (users might do) will be ensured not to get lost when the framework is updated to newer releases. Glorp is a typical example how ugly a Smalltalk code gets, when porting issues are more important – but beside this Glorp is a brilliant sotware, without any question: just don’t get me wrong here. But the code does not feel like VASmalltalk code.
An idea for Glorp under VA: move the VADatabaseAccessor class to GlorpVAPort to get more freedom to make VA programming.
Ok, I tried to write the VA-database layer (which is more or less undocumented and pretty boring code) for SQLite (MSKSQLiteWrapperApp), but according to users (Hello Igor !) there are some errors in it and I did not have time to fix these errors – simply because of the fact, that I did not use this wrapper code by myself. I wrote it, did some very simple applications and that was it. Users are invited to pick up this code, rewrite or write complete new code …. :-)))
Because of this the AbtLayer for the PostgreSQL wrapper is still missing ……..
Ok – enough with all those background information about the MSKSQLiteWrapper.