joost 21dde458f5 + Fix bug #4376, varchar without size specification před 20 roky
..
examples 22e17d51db + recreate is not supported by postgres před 20 roky
interbase 2dbdc474fd * use register variables when release-building for ppc (more or less doubles před 20 roky
mysql 2dbdc474fd * use register variables when release-building for ppc (more or less doubles před 20 roky
postgres 21dde458f5 + Fix bug #4376, varchar without size specification před 20 roky
Makefile 2dbdc474fd * use register variables when release-building for ppc (more or less doubles před 20 roky
Makefile.fpc 86f78c7300 * units are now created in separate directory units/cpu-os/ před 21 roky
fpmake.inc cc4818be26 + initial implementation of new fpmake compile tools před 20 roky
fpmake.pp cc4818be26 + initial implementation of new fpmake compile tools před 20 roky
readme.txt 7950c3ae5e * added a rough-readme to sqldb před 20 roky
sqldb.pp 294bf06cda - Fix to allow changing the filter while filtered před 20 roky
testsqldb.pp 790a4fe2d3 * log and id tags removed před 20 roky

readme.txt

SQLDB readme file, 20 Aug 2005, Joost van der Sluis

since there is no real documentation about sqldb yet, this should be regarded as
a small reminder to myself, and to others who want to write their own
connections.

From the TSQLConnection point-of-view the following methods are called if a
select-statement is used:

OPEN:
Prepare: (is only called when prepared is false)
- AllocateCursorHandle (only if the cursor <> nil)
- Preparestatement
Execute:
- Execute
- AddFieldDefs (only if called for the first time after a prepare)

GETNEXTPAKCET: (probably called several times, offcourse)
- Fetch
- Loadfield

CLOSE:
- FreeFieldBuffers
- UnPrepareStatement (Only if prepare is False, thus if prepared queries
were not supported)
UnPrepare:
- UnPrepareStatement

DESTROY:
- DeAllocateCursorHandle (Also called if the Connection is changed)


From the TSQLConnection point-of-view the following methods are called if a non-
select-statement is used (execsql):

Prepare: (is only called when prepared is false)
- AllocateCursorHandle (only if the cursor <> nil)
- Preparestatement

Execute:
- Execute
- UnPrepareStatement (Only if prepare is False, thus if prepared queries
were not supported)


UNPREPARE:
- UnPrepareStatement

DESTROY:
- DeAllocateCursorHandle (Also called if the Connection is changed)


A short description of what each method in a TSQLConnection should do:

* Function AllocateCursorHandle : TSQLCursor; override;

This function creates and returns a TSQLcursor which can be used by any query
for the used type of database. The cursor is only database-dependent, it is
deallocated when the connection of the query changes, or if the query is
destroyed.

* Procedure DeAllocateCursorHandle(var cursor : TSQLCursor); override;

This function deallocates the TSQLCursor, and sets its value to nil.

* procedure PrepareStatement(cursor: TSQLCursor;ATransaction : TSQLTransaction;buf : string; AParams : TParams); override;

This functions prepares the query which is given in buf.

It's only called if Prepared is True.
If the database supports prepared queries for the kind of sql-statement (in
cursor.FStatementType) and the prepare was successfully, then cursor.FPrepared
is set to True, so that prepare will not be called again, until UnPrepared
is called. (which sets FPrepared to False)

* procedure FreeFldBuffers(cursor : TSQLCursor); override;

This procedure is called if a Select-query is closed. This procedure is used to
handle all actions which are needed to close a select-statement.