Przemek:
>Any you want. DBT allows to store only strings and uses 512 bytes
>blocks. FPT allows to store also other data types (numbers, dates,
>arrays, ...) and user can set block size (default is 64 bytes) so it's
>more flexible and creates smaller files.
>It also contains garbage collector which allow to reuse freed regions.
>SMT is SIX3 format which have most of FPT features.
>All formats are recognized by Harbour. In fact it even recognize
>different implementations of FPT formats which can be controlled by:
> rddInfo( RDDI_MEMOVERSION, DB_MEMOEXT_* [, <cRDD>] )
Some weeks ago I posted a question based on tests:
-----------------------------
? "SET( _SET_MFILEEXT )", SET( _SET_MFILEEXT )
? "SET( _SET_MBLOCKSIZE )", SET( _SET_MBLOCKSIZE )
? "SET( _SET_AUTORDER )", SET( _SET_AUTORDER )
? "SET( _SET_AUTOPEN )", SET( _SET_AUTOPEN )
? "DBINFO( DBI_MEMOBLOCKSIZE )", DBINFO( DBI_MEMOBLOCKSIZE )
e) Results with Clipper 5.3a, as expected (not create/add, just values
and record pointer "movement")
SET( _SET_MFILEEXT )
SET( _SET_MBLOCKSIZE ) 64
SET( _SET_AUTORDER ) 0
SET( _SET_AUTOPEN ) .T.
DBINFO( DBI_MEMOBLOCKSIZE ) 64
f) Results with Harbour
NTFS:
------
SET( _SET_MFILEEXT )
SET( _SET_MBLOCKSIZE ) 0
SET( _SET_AUTORDER ) 0
SET( _SET_AUTOPEN ) .T.
DBINFO( DBI_MEMOBLOCKSIZE ) 64
------
g) Why Clipper and Harbour show different ? :
SET( _SET_MBLOCKSIZE ) 64
SET( _SET_MBLOCKSIZE ) 0
It must be fixed ?
-----------------------------
If some old (Clipper) application rely on SET( _SET_MBLOCKSIZE ) result,
then will fail in Harbour behaviour
David Macias
_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
