| verzia 1.29, 2003/04/07 00:53:28 |
verzia 1.30, 2003/04/18 13:29:22 |
|
|
| <!-- $Platon: phpMyEdit/doc/sgml/configuration.general.sgml,v 1.28 2003/04/06 19:32:33 nepto Exp $ --> |
<!-- $Platon: phpMyEdit/doc/sgml/configuration.general.sgml,v 1.29 2003/04/07 00:53:28 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 431 $opts['filters'] = 'column1 like "%11%" |
|
| Riadok 431 $opts['filters'] = 'column1 like "%11%" |
|
| |
|
| $opts['filters'] = 'section_id = 9'; |
$opts['filters'] = 'section_id = 9'; |
| |
|
| $opts['filters'] = 'Table0.sessions_count > 200'; |
$opts['filters'] = 'PMEtable0.sessions_count > 200'; |
| ]]></programlisting> |
]]></programlisting> |
| </example> |
</example> |
| |
|
| </para> |
</para> |
| <para> |
<para> |
| |
|
| |
When generating query, &name; redefines/aliases the table names for easy |
| |
accessing of particular table fields in the main table and in the tables used |
| |
in JOIN clausules as well. The main table name is changed to <database |
| |
class=table>PMEtable0</>, tables used in JOIN clausules have their name like |
| |
<database class=table>PMEjoinN</> where <varname>N</> is JOIN table order. |
| |
|
| |
</para> |
| |
<para> |
| |
|
| |
We recommend you to look at generated SQL queries in your MySQL log file in |
| |
order you want to know how database table was aliased. Finally, described |
| |
approach is needed only if you are accessing field, which name occurs in more |
| |
than one table of SQL query (thus MySQL cannot exactly determine what it is |
| |
meant with "field_name"). |
| |
|
| |
</para> |
| |
<para> |
| |
|
| For future is planned initialization like the following one. |
For future is planned initialization like the following one. |
| |
|