Another hint for creating primary/unique keys.
This commit is contained in:
@@ -5,6 +5,9 @@ phpMyAdmin - Changelog
|
||||
$Id$
|
||||
$Source$
|
||||
|
||||
2003-10-07 Michal Cihar <nijel@users.sourceforge.net>
|
||||
* Documentation: Another hint for creating primary/unique keys.
|
||||
|
||||
2003-10-06 Marc Delisle <lem9@users.sourceforge.net>
|
||||
* lang/slovak: Updated, thanks to Lubos Klokner (erkac).
|
||||
|
||||
|
@@ -2733,6 +2733,19 @@ To create a new, empty mimetype please see libraries/transformations/template_ge
|
||||
LEFT JOIN from the foreign table.
|
||||
</p>
|
||||
|
||||
<h4>
|
||||
[3.7] I have table with many (100+) fields and when I try to browse table
|
||||
I get series of errors like "Warning: unable to parse url". How
|
||||
can this be fixed?
|
||||
</h4>
|
||||
<p>
|
||||
Your table neither have a primary key nor an unique one, so we must use a
|
||||
long expression to identify this row. This causes problems to parse_url
|
||||
function. The workaround is to create a primary or unique key.
|
||||
<br />
|
||||
</p>
|
||||
|
||||
|
||||
<a name="faqmultiuser"></a><br />
|
||||
<h3>[4. ISPs, multi-user installations ]</h3>
|
||||
|
||||
|
@@ -6,7 +6,7 @@
|
||||
Transformations - FAQ - Developers - Credits - Translators
|
||||
______________________________________________________________________
|
||||
|
||||
phpMyAdmin 2.5.4-rc1 Documentation
|
||||
phpMyAdmin 2.5.5-dev Documentation
|
||||
|
||||
* SourceForge phpMyAdmin project page [ http://www.phpmyadmin.net/
|
||||
]
|
||||
@@ -14,8 +14,8 @@
|
||||
+ Version history: ChangeLog
|
||||
+ General notes: README
|
||||
+ License: LICENSE
|
||||
* Documentation version: $Id: Documentation.html,v 1.504 2003/10/01
|
||||
01:58:16 lem9 Exp $
|
||||
* Documentation version: $Id: Documentation.html,v 1.506 2003/10/01
|
||||
07:37:53 rabus Exp $
|
||||
|
||||
Requirements
|
||||
|
||||
@@ -1892,6 +1892,15 @@ FAQ - Frequently Asked Questions
|
||||
In Query-by-example (Query), automatic generation of the query LEFT
|
||||
JOIN from the foreign table.
|
||||
|
||||
[3.7] I have table with many (100+) fields and when I try to browse table I
|
||||
get series of errors like "Warning: unable to parse url". How can this be
|
||||
fixed?
|
||||
|
||||
Your table neither have a primary key nor an unique one, so we must
|
||||
use a long expression to identify this row. This causes problems to
|
||||
parse_url function. The workaround is to create a primary or unique
|
||||
key.
|
||||
|
||||
[4. ISPs, multi-user installations ]
|
||||
|
||||
[4.1] I'm an ISP. Can I setup one central copy of phpMyAdmin or do I need
|
||||
@@ -2236,7 +2245,7 @@ FAQ - Frequently Asked Questions
|
||||
If you put a backslash before the underscore, it means that the
|
||||
database name will have a real underscore.
|
||||
|
||||
[6.11] What is the curious symbol <EFBFBD> in the statistics pages?
|
||||
[6.11] What is the curious symbol o/ in the statistics pages?
|
||||
|
||||
It means "average".
|
||||
|
||||
@@ -2269,7 +2278,7 @@ FAQ - Frequently Asked Questions
|
||||
If you use it, you should be aware that any SQL statement you submit
|
||||
will be stored anonymously (database/table/column names, strings,
|
||||
numbers replaced with generic values). The Mimer SQL Validator itself,
|
||||
is <EFBFBD> 2001 Upright Database Technology. We utilize it as free SOAP
|
||||
is (c) 2001 Upright Database Technology. We utilize it as free SOAP
|
||||
service.
|
||||
|
||||
[6.15] I want to add a BLOB field and put an index on it, but MySQL says
|
||||
@@ -2516,7 +2525,7 @@ CREDITS, in chronological order
|
||||
* current project maintainer
|
||||
* many bugfixes and improvements
|
||||
|
||||
- Lo<EFBFBD>c Chapeaux <lolo_at_phpheaven.net>
|
||||
- Loic Chapeaux <lolo_at_phpheaven.net>
|
||||
* rewrote and optimized javascript, DHTML and DOM stuff
|
||||
* rewrote the scripts so they fit the PEAR coding standards and
|
||||
generate XHTML1.0 and CSS2 compliant codes
|
||||
|
Reference in New Issue
Block a user