J
Jamey Cribbs
KirbyBase 1.4 is now available at:
http://www.netpromi.com/files/KirbyBase-1.4.zip
What is KirbyBase?
KirbyBase is a simple, pure-Python, plain-text, flat-file database
management system that can be used either embedded in your application
or in a client/server, multi-user mode.
To find out more about KirbyBase, go to:
http://www.netpromi.com/kirbybase.html
Changes:
Added two new database field types: datetime.date and
datetime.datetime. They are stored as strings, but are input and output
as instances of datetime.date and datetime.datetime respectively. You
can use them just like any other field: you can use them as selection
criteria (i.e. db.select('plane.tbl', ['began_service'], ['>=%s' %
datetime.date(1937,12,31)) or use them to specify the sort order of the
result set of a select statement (i.e. db.select('plane.tbl', ['name'],
['.*'], sortField='range', ascending=False)).
Made a few internal optimizations when running queries that have
resulted in a 15-20% speed increase when doing large queries or updates.
Changed the name of all private methods from starting with two
underscores to starting with one underscore based on a discussion in
comp.lang.python as to how to properly name private variables.
http://www.netpromi.com/files/KirbyBase-1.4.zip
What is KirbyBase?
KirbyBase is a simple, pure-Python, plain-text, flat-file database
management system that can be used either embedded in your application
or in a client/server, multi-user mode.
To find out more about KirbyBase, go to:
http://www.netpromi.com/kirbybase.html
Changes:
Added two new database field types: datetime.date and
datetime.datetime. They are stored as strings, but are input and output
as instances of datetime.date and datetime.datetime respectively. You
can use them just like any other field: you can use them as selection
criteria (i.e. db.select('plane.tbl', ['began_service'], ['>=%s' %
datetime.date(1937,12,31)) or use them to specify the sort order of the
result set of a select statement (i.e. db.select('plane.tbl', ['name'],
['.*'], sortField='range', ascending=False)).
Made a few internal optimizations when running queries that have
resulted in a 15-20% speed increase when doing large queries or updates.
Changed the name of all private methods from starting with two
underscores to starting with one underscore based on a discussion in
comp.lang.python as to how to properly name private variables.