verzia 1.42, 2004/05/17 10:55:38 |
verzia 1.43, 2004/07/15 10:40:23 |
|
|
<!-- $Platon: phpMyEdit/doc/sgml/configuration.general.sgml,v 1.41 2004/04/21 14:36:40 nepto Exp $ --> |
<!-- $Platon: phpMyEdit/doc/sgml/configuration.general.sgml,v 1.42 2004/05/17 10:55:38 nepto Exp $ --> |
|
|
<sect1 id="configuration.mysql-options"> |
<sect1 id="configuration.mysql-options"> |
<title id="configuration.mysql-options.title">Database connection</title> |
<title id="configuration.mysql-options.title">Database connection</title> |
Riadok 30 $opts['tb'] = 'table'; |
|
Riadok 30 $opts['tb'] = 'table'; |
|
</para> |
</para> |
<para> |
<para> |
|
|
It is recommended that the first four options shown above be moved to a |
Recommended usage is, that the first four options shown above should be moved |
separate, included file. |
to a separate, included file. |
|
|
|
</para> |
|
<para> |
|
|
|
It is rather common situation to use &name; inside larger project. To prevent |
|
&name; before creation of another persistent database connection, you can |
|
supply <varname>$opts['dbh']</varname> option, where valid allocated MySQL |
|
database handle is expected. In this case, the first four options written |
|
above are completelly ignored. Only table name is used. |
|
|
|
</para> |
|
<para> |
|
|
|
<example><title>Supplying allocated connection</title> |
|
<programlisting><![CDATA[ |
|
$opts['dbh'] = $your_project_db_handle; |
|
]]></programlisting> |
|
</example> |
|
|
</para> |
</para> |
</sect1> |
</sect1> |