Store with SQLite

Dear Shiro,

I started using SQLite for Store in wv8.0 Windows 7 and found it very
convenient to use for Store in a single user environment. There is no need
to run a server program. All the information is stored in one file. This
makes backup and moving data base among computers simple and reliable.

I use 32 bit vm in 64 bit OS, so copied 32 bit sqlite3.dll in
"\Windows\SysWOW64\"

"Source Code Management Guide P46-0138-09" has errors in Configuring
Store/SQLite Setup in page 3-7.

At Step 3.
*For the database Environment string, enter the absolute or relative*
*(to the current VisualWorks image directory) location where the*
*SQLite database file should be created.*

I found the string must be a database table name, not the location.

Do you mean it must be the full filename, not just the directory location in which the file resides?  That is correct (and is the intended meaning of the text).

(What you actually write implies the filename needs to be the name of a table in the database but that is not so and I assume that is not what you mean.).

If only
a table name is entered, the table is made in the image directory. If the
table be created in another directory, the full path must be entered, such
as "C:\\Cincom\\Store\\StoreTable" (in Windows environment, back slashes
must be doubled as they are treated as escape character).
 

Doubling of \ is not needed in my Windows environment:  both
   C:\Cincom\Store\SomeTableName
and
   C:\Cincom\Store\SomeOtherFilename
work fine for me.

At Step 9.
*When you are prompted for a database identifier, enter a string*
*that will uniquely identify this Store database within your*
*organization.*

I think this database identifier is ignored. What counts is the database
table name in Environment string.
 

You will see this string in Store and RB windows in your image, identifying the database you are looking at or the database(s) to which your packages are reconciled.  You are quite right that the Store Connection dialog accepts the full or relative path.  What I assume you mean is that the Store connection-defining code does not call #addLogical:environment: so that if you create a database in
   C:\Cincom\Store\MyFilename.db
and give it Store name
   'ShiroStoreDB'
then you will see 'ShiroStoreDB' in the title bar of a published components window when connected to it but you will not be able to replace
   C:\Cincom\Store\MyFilename.db
with
   'ShiroStoreDB'
in your Store connection dialog.  This could be added;  it would need calls of #addLogical:environment: and #removeLogical: to be hooked into the Store connection-creation dialog.  I'm guessing the reason it has not been is that most people simply save their Store connection when they first define it, so finding it in the drop-down is even easier than a short logical name would be.

James Robertson's video,
http://www.jarober.com/blog/blogView?showComments=true&printTitle=Setting_Up_Store_for_SQLite&entry=3451210218
,

which Aik-Siong Koh mentioned, was very helpful. Thanks James, I wish you
kept doing webcasting.
 

Sadly, James died about a year ago.  I too feel the loss of his contributions, and his engaging personality.

           HTH
                  Niall Ross