We add support for FoxPro datetime fields, which store an exact
timestamp in two binary dwords, representing the Julian day number and
the number of milliseconds since midnight, respectively. These are
represented in userland as strings with the format "YYYYMMDDhhmmss.uuu",
which conforms to ISO-8601.
According to the current handling of date fields, the validity of input
and output is not checked, i.e. it is possible to store invalid datetime
values in the database. If necessary, respective checks have to be made
by the programmer.
To avoid reinventing the wheel, but also not to rely on ext/calendar, we
add the respective functionality and adapt the names to avoid build
conflicts.
git-svn-id: http://svn.php.net/repository/pecl/dbase/trunk@340796 c90b9560-bf6c-de11-be94-00142212c4b1
The open mode values might be implementation-dependend, so we make
DBASE_RDONLY and DBASE_RDWR available to userland.
git-svn-id: http://svn.php.net/repository/pecl/dbase/trunk@340746 c90b9560-bf6c-de11-be94-00142212c4b1
The database handles should be really opaque to userland, and not only
treated as such, to avoid confusion and bugs. This appears to be
particularly relevant as of PHP 7.0.0 which introduces `int` type hints.
We consider the BC break to be relatively small; quite likely only some
tests would be affected (as can be seen in our test suite). And, anyhow,
we're working on a new major version, so at least some BC breaks are to
be expected.
Objects would be an alternative, but without methods they won't be a
real improvement over resources, so we leave that for a future version.
git-svn-id: http://svn.php.net/repository/pecl/dbase/trunk@340743 c90b9560-bf6c-de11-be94-00142212c4b1
Christoph Michael Becker