Playing with SQLite, I decided to write a simple example, that to help people willing to use excelent (only not so small) database engine SQLite.
In order to keep it as simple as possible, there is no any error check in the example.

[EDIT]This example is included in the latest Fresh release (1.1.D), in the directory "examples".[/EDIT]

Regards.

I actually use SQLite for all my SQL needs -- it is very fast, and works on Linux and Win32 equally well. An excellent library, and actively developed (and completely free, like FASM).

Only shame is it's not written in FASM

Well, it is still not too late...

But actually SQL is not very compatible with assembler way of thinking... I suppose, if someone want to create RDBMS, suitable for assembly language programming, he/she would be better to choose some different approach - flexible as SQL, but more assembly-like...who knows, maybe something like Forth or at least - SQL, but not string based...

Regards.

john, is the file still available the link leads to an error page

Sorry, guys. I simply forgot to remove this link. It is obsolete, because I included this example in the latest Fresh release, "examples" directory.

Regards

hi john,
they released some new version of sqlite3.dll

maybe you could update the examples zip

http://www.sqlite.org/download.html

your is 236 KB (241,664 bytes) and the current released on their site is 241 KB (246,784 bytes).

sincerely,
sulaiman chang.

* i gonna take a look on ur sqlite example,coz the VB torture me very much already!

Hi, vbVeryBeginner.

I know there is new version(s). In the next release of Fresh it will be updated, of course. But actually as far as the API is the same, you simply can replace old .dll with new one and the example will work the same way.

Regards.

yup, replace them already
btw, could you make the example (all the proc calls) in one file instead of having procs in several files?, coz it might be easier for non-fresh user to enjoy that great example ?

btw, how bout the cdecl and stdcall problem?
i replace the sqlite3.dll and found that they got no problem? but u said they r using cdecl calling in one thread? and need to do something with the stack?? care to explain to me (i am quite beginner on this)


at first i thought the size difference is because u recompile the sqlite source again to stdcall convention.. ??

I wouldn't call it a "problem". There are working macroses "ccall" and "cinvoke" in "StrCallEx.inc", so you can call any cdecl function without any problem.
I simply don't like this convention, because it is not too reasonable, except for several particular cases - for example if you want to pass different number of arguments to one procedure.

Regards