| version 1.21, 2003/03/25 21:32:21 |
version 1.22, 2003/03/26 18:32:42 |
|
|
| <!-- $Platon: phpMyEdit/doc/sgml/configuration.general.sgml,v 1.20 2003/03/18 00:50:22 nepto Exp $ --> |
<!-- $Platon: phpMyEdit/doc/sgml/configuration.general.sgml,v 1.21 2003/03/25 21:32:21 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> |
| Line 45 The unique identifier, or record ID, cho |
|
| Line 45 The unique identifier, or record ID, cho |
|
| --> |
--> |
| |
|
| Assuming that 'id' is the name of the MySQL column selected as the unique |
Assuming that 'id' is the name of the MySQL column selected as the unique |
| identifier when <filename>phpMyEditSetup.php</filename> was run, the key |
identifier when <filename>phpMyEditSetup.php</filename> script was run, the |
| will appear in the script as: |
key will appear in the script as: |
| |
|
| </para> |
</para> |
| <para> |
<para> |
| Line 63 $opts['key'] = 'id'; |
|
| Line 63 $opts['key'] = 'id'; |
|
| |
|
| <important><para> |
<important><para> |
| |
|
| There were problems reported by &name; users regarding using MySQL reserved |
There were problems reported by &name; users regarding to usige of MySQL |
| word as unique key name (the example for this is "key" name). Thus we |
reserved word as an unique key name (the example for this is "key" name). Thus |
| recommend you to use another name of unique key. Usage of "id" or "ID" should |
we recommend you to use another name of unique key. Usage of "id" or "ID" |
| be safe and good idea. |
names should be safe and good idea. |
| |
|
| </para></important> |
</para></important> |
| |
|