Opensource.Platon.SK CVS: phpMyEdit/doc/sgml/configuration.general.sgml - diff

Up to [Platon] / phpMyEdit / doc / sgml

Diff for phpMyEdit/doc/sgml/configuration.general.sgml between version 1.4 and 1.5

version 1.4, 2002/12/11 18:27:55

version 1.5, 2002/12/11 23:36:52

Line 1

<title id="configuration.mysql-options.title">Database connection</title>

Line 90 possible unique key types are 'real' or

If you are using 'real' key type and some problems with record manipulaton have

occured, it is probably because your MySQL key datatype is 'float'. Comparsions

with this datatype is common problem in most computer languages (SQL including),

with this datatype is a common problem in most computer languages (SQL including),

because floating-point values are not exact values. In most cases, changing

MySQL datatype from 'float' to 'double' and preserving 'real' as &name; key type

should solve this problem.

Line 218 Other URLs for another elements may be a

<title id="configuration.code-execution.title">Code execution</title>

<para>

Since version 4.0 &name; will automatically starts its execution.

Since version 4.0, &name; automatically starts its execution.

You can turn this feature off by setting:

<example><title>Turning off default execution</title>

Line 314 administrator with the ability to delete

Line 313 administrator with the ability to delete

&name; offers powerful default and/or additional sorting capabilities via

<varname>$opts['sort_field']</varname> option. You can define column name or

column field number you'd prefer to sort on when the script is first loaded. To

get descending sort order, prefix column name or field number with dash (-)

get descending sort order, prefix the column name or field number with dash (-)

sign. Look at few following examples:

sign. Look at the following examples:

<example><title>Sort field option</title>

<programlisting><![CDATA[

Line 343 $opts['sort_field'] = array('company', '

Line 342 $opts['sort_field'] = array('company', '

</para>

<para>

Also note, that &name; sorting feature is cumulative. This exactly mean, that if

Also note that &name;'s sorting feature is cumulative. This means, that if

default sort fields are specified and user selects (clicks) to sort by another

default sort fields are specified and the user selects (clicks) to sort by

column in table listing screen, resulting screen will be sorted by user selected

another column in table listing screen, the resulting screen will be sorted by

column first and than by specified default sort fields. Next click on another

user selected column first and then by specified default sort fields. Next

sort column will again force to sort table by selected column first. Previously

click on another sort column will again force to sort table by selected column

selected fields or default ones will follow up in sorting sequence.

first. Previously selected fields or default ones will follow up in sorting

sequence.

</para>

<para>

Line 483 not 'transaction-safe'.

</para>

<para>

Triggers are risky in basic MySQL as there is no native transaction support--it

Triggers are risky in basic MySQL as there is no native transaction support. It

is not transaction-safe by default. There are transaction-safe table types in

MySQL that can be conditionally built (see MySQL-Max), but &name; is currently

not set up to support real transactions. What that means is that if an

Line 504 They _must_ return true or false to indi

</para>

<para>

<example><title>Triggers ussage</title>

<example><title>Triggers usage</title>

<programlisting><![CDATA[

$opts['triggers']['insert']['before']='categories.TIB.inc';

$opts['triggers']['insert']['before'] = 'categories.TIB.inc';

$opts['triggers']['insert']['after'] ='categories.TIA.inc';

$opts['triggers']['insert']['after'] = 'categories.TIA.inc';

$opts['triggers']['update']['before']='categories.TUB.inc';

$opts['triggers']['update']['before'] = 'categories.TUB.inc';

$opts['triggers']['update']['after'] ='categories.TUA.inc';

$opts['triggers']['update']['after'] = 'categories.TUA.inc';

$opts['triggers']['delete']['before']='categories.TDB.inc';

$opts['triggers']['delete']['before'] = 'categories.TDB.inc';

$opts['triggers']['delete']['after'] ='categories.TDA.inc';

$opts['triggers']['delete']['after'] = 'categories.TDA.inc';

]]></programlisting>

</example>

Line 597 Available languages are:

<title id="configuration.cgi-variables.title">CGI variables</title>

<para>

You can optionally append or overwrite particular variables returned from CGI

You can optionally append or overwrite particular variables returned from the

environment (GET/POST HTTP protocol data). Use these two arrays for this

CGI environment (GET/POST HTTP protocol data). Use these two arrays for this

purpose, where array key mean CGI variable name and value means CGI variable

value.

</para>

<para>

This will cause descending sorting according first field if other type of sort

This will turn on search filter on script initialization. However, it is

was not specified/selected by user.

still possible to turn it off by explicit click on <GUIbutton>Hide</> or

<GUIbutton>Clear</> button.

<example><title>CGI variables appending</title>

<programlisting><![CDATA[

$opts['cgi']['append'] = array('sfn' => '-0');

$opts['cgi']['append']['fl'] = 1

]]></programlisting></example>

</para>

<para>

This will cause the same sort allways in all cases.

Next example shows how to cause descending sorting according first field in all

cases. Because <varname>['overwrite']</varname> is used, sorting column cannot

be altered by user by clicking on column heading.

<example><title>CGI variables overwriting</title>

<programlisting><![CDATA[

$opts['cgi']['overwrite'] = array('sfn' => '-0');

$opts['cgi']['overwrite']['sfn'] = '-0';

]]></programlisting></example>

</para>

Platon Group <platon@platon.org> http://platon.org/


Copyright © 2002-2006 Platon Group Site powered by Metafox CMS	Go to Top