[Mybusinessbasic-devel] Re: Thoughts on file types and I/O

[Montgomery T. <MTi...@ca...>]

Howdy,

>1)  Indexed files should be easy enough to implement using some of the
> functions from the PBL Base functions.

has the decision been made that PBL will be used as the DB library? if
not, i suggest you look at the miniDB library
http://www.atbas.org/minidb/index.php . one thing that i like better
about miniDB is that it will allow you to create/build/delete indices on
the fly.


>5)  We should add a "DIR=3D" function to be used in READ statements =
that
will
> indicate the direction of the read.

i think you are asking for BBx compatible commands/features, and i
agree.


> 6)  Fields in Multi-keyed files should be named and access should be
> permitted by name as well as by field number.  For instance if field
number
> 8 in a file is named "Partnum" then an IOLIST could be written as
either
> "IOLIST #8=3DPART$" or "IOLIST #PARTNUM=3DPART$" or more traditionally =
as
> "IOLIST *,*,*,*,*,*,*,PART$"
>=20
> 7)  Fields in direct files should not be named and access should be
> permitted only by field number.  For instance if field number 8 in a
file
> contains the "Partnum" information then an IOLIST could be written as
either
> "IOLIST #8=3DPART$" or more traditionally as "IOLIST
*,*,*,*,*,*,*,PART$"
=20
are these features that other BB's have, or is this something new? the
use of "should" comes across rather heavy. i'd rather not see this as a
requirement. (maybe i'm reading too much into "should" :)


>8)  The key fields in multi-keyed files can be used in the "KEY=3D"
function
> to specify which of the keys to use for access.  For instance if the
> "Partnum" field is designated as a key field then a read command could
be
> written as follows "READ (1,KEY=3D#PARTNUM=3DPART$)A1$,A2$,A3$..." or =
as
"READ
> (1,KEY=3D#8=3DPART$)A1$,A2$,A3$..."
=20
i suggest the use of the BBx syntax of "KNUM=3DX". where X is generally =
a
number, but could be expanded to accept "#PARTNUM".



                              \\//_