cvs: peardoc /en/package/authentication liveuser.xml

lsmith Thu Aug 11 05:50:02 2005 EDT Modified files: /peardoc/en/package/authentication liveuser.xml Log: - added note about db schema and permission container complexity levels http://cvs.php.net/diff.php/peardoc/en/package/authentication/liveuser.xml?r1=1.7&r2=1.8&ty=u Index: peardoc/en/package/authentication/liveuser.xml diff -u peardoc/en/package/authentication/liveuser.xml:1.7 peardoc/en/package/authentication/liveuser.xml:1.8 --- peardoc/en/package/authentication/liveuser.xml:1.7 Thu Aug 11 05:38:54 2005 +++ peardoc/en/package/authentication/liveuser.xml Thu Aug 11 05:49:57 2005 @@ -1,4 +1,4 @@ -<!-- $Revision: 1.7 $ --> +<!-- $Revision: 1.8 $ --> <sect1 id="package.authentication.liveuser"> <title>LiveUser</title> <refentry id="package.authentication.liveuser.liveuser-summary"> @@ -72,6 +72,11 @@ Before you can use LiveUser you will need to setup the necessary data structures for the chosen container. Through the use of the configuration options it is possible to customize alot of the aspects of the storage layer. Most notably it is possible to alias field and table names. This should make it possible to integrate any legacy data into LiveUser. Depending on the container chosen you may have to use the database schema installer. The installer requires the MDB2_Schema and MDB2 packages and is able to handle most configuration options properly to be able to install the database schema directly into your database. During the installation process the installer will create backup files of the installed schema. These files will enable the installer to attempt to alter the database if run again with a different configuration. However if these files exist the installer will always attempt to alter instead of creating the tables from scratch as long as you are using the sam DSN. If for some reason you need to create the tables from scratch again then please delete the backup files with the matching DSN. You can find the installer inside the data directory of your pear install directory. Its called install.php and at the top of the file you will find a number of sample API calls which are commented out. +An ER diagram of the database structure can be found here: +http://www.backendmedia.com/LiveUser/liveuser_db_schema.png + +The diagram details what tables are needed for what permission complexity level. If you want to prevent the installer from installing tables you dont need you can modify the "tables" property of the instance of the permission container you pass to the generateSchema() method in the installer. + In order to get started with LiveUser the following two articles should help in getting off the ground: http://jystewart.net/process/archives/2005/07/configuring-liveuser http://jystewart.net/process/archives/2005/08/getting-started-with-liveuser-permissions/