i do not know how this changed in the version published, but it has been changed. In a previously email I outlined the problem under OSX which manifests itself in the terminal application, not just my build under x-code. In that email I show the terminal application log of commands and responses.
BTW, OSX in most cases accepts either forward slashes or colans as the path delimiter.
Perhaps someone else can verify the problem under OSX. The open command however does not work as expected.
> I also have another problem stemming from version 3. The open command seems
> not to work with the API. In other words, if the OS is mac and I pass colans
> as the path delimiter, I end up getting a file name with slashes. if I pass
> a path name with forward slashes as the delimiter then I get an error. . .
> and sometimes I get no error returned, but still no file is created. So it
> seems that the new way of opening (and creating where the file is not created
> immediately) has broken something. Any ideas?
>
SQLite version 3.0 does not work with Mac OS-9 since nobody has ever submitted
drivers for it. There is a file named "os_mac.c" in the distribution, but it
busted. If you want to use OS-9 you'll need to stick with SQLite version 2.8.
