1d497297cd
there are no core and extensions packages anymore, everything is built by
the main ports itself and the package names have changed to php-${V} or
php-mysql-${V} for modules.
The new ports allows you to install all of the php versions just like python
so you can actually run different webservers with different versions of php
because you can't load two modules to one. You can only do that with fastcgi.
The port tries to share all the files that can be shared and the different
extensions are located in the local version's Makefile instead of Makefile.inc.
The other change is that *all* of the configuration has moved to /etc out
of /var/www because that was a realy stupid concept, since apache if you
use it chrooted, will load all of the extensions before doing the actual
chroot.
This port is not linked to the build yet because several issues have to
be resolved first, like providing a way to update from php5-* packages,
and probably other things that do not come into my mind right now,
because the Bullfrog is making me crazy.
18 lines
777 B
Plaintext
18 lines
777 B
Plaintext
These functions allow you to access records stored in dBase-format
|
|
(dbf) databases.
|
|
|
|
There is no support for indexes or memo fields. There is no support
|
|
for locking, too. Two concurrent webserver processes modifying the
|
|
same dBase file will very likely ruin your database.
|
|
|
|
dBase files are simple sequential files of fixed length records.
|
|
Records are appended to the end of the file and delete records are
|
|
kept until you call dbase_pack().
|
|
|
|
We recommend that you do not use dBase files as your production
|
|
database. Choose any real SQL server instead; MySQL or Postgres are
|
|
common choices with PHP. dBase support is here to allow you to
|
|
import and export data to and from your web database, because the
|
|
file format is commonly understood by Windows spreadsheets and
|
|
organizers.
|