Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
M
mariadb
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
mariadb
Commits
3a9fa2ac
Commit
3a9fa2ac
authored
Apr 13, 2002
by
unknown
Browse files
Options
Browse Files
Download
Plain Diff
Merge work.mysql.com:/home/bk/mysql-4.0
into george.bitbike.com:/home/arjen/mysql-4.0
parents
87ece1fa
783217fd
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
7 additions
and
32 deletions
+7
-32
Docs/manual.texi
Docs/manual.texi
+7
-32
No files found.
Docs/manual.texi
View file @
3a9fa2ac
...
@@ -1756,7 +1756,7 @@ new features. Additional features will be incorporated into
...
@@ -1756,7 +1756,7 @@ new features. Additional features will be incorporated into
MySQL 4.0.1, 4.0.2 onwards; very probably within a couple of months,
MySQL 4.0.1, 4.0.2 onwards; very probably within a couple of months,
MySQL 4.0 will be labelled beta. Further new features will then
MySQL 4.0 will be labelled beta. Further new features will then
be added in MySQL 4.1, which is targeted for alpha release
be added in MySQL 4.1, which is targeted for alpha release
in
early
2002.
in
third quarter
2002.
@node Nutshell Ready for Immediate Development Use, Nutshell Embedded MySQL, Nutshell Stepwise Rollout, MySQL 4.0 In A Nutshell
@node Nutshell Ready for Immediate Development Use, Nutshell Embedded MySQL, Nutshell Stepwise Rollout, MySQL 4.0 In A Nutshell
...
@@ -4780,7 +4780,7 @@ MySQL Server offers the following advantages over PostgreSQL:
...
@@ -4780,7 +4780,7 @@ MySQL Server offers the following advantages over PostgreSQL:
@itemize @bullet
@itemize @bullet
@item
@item
@code{MySQL} Server is generally much faster than PostgreSQL. MySQL
@code{MySQL} Server is generally much faster than PostgreSQL. MySQL
4.0.1
has also
a query cache that can boost up the query speed for
4.0.1
also has
a query cache that can boost up the query speed for
mostly-read-only sites many times.
mostly-read-only sites many times.
@item
@item
...
@@ -4963,29 +4963,6 @@ same time. @xref{DELETE}.
...
@@ -4963,29 +4963,6 @@ same time. @xref{DELETE}.
PostgreSQL currently offers the following advantages over MySQL Server:
PostgreSQL currently offers the following advantages over MySQL Server:
Note that because we know the MySQL road map, we have included in the
following table the version when MySQL Server should support this feature.
Unfortunately we couldn't do this for previous comparison, because we
don't know the PostgreSQL roadmap.
@multitable @columnfractions .35 .30
@item @strong{Feature} @tab @strong{MySQL version}
@item Subselects @tab 4.1
@item Foreign keys @tab 4.0 and 4.1
@item Views @tab 4.2
@item Stored procedures @tab 4.1
@item Extensible type system @tab Not planned
@item Unions @tab 4.0
@item Full join @tab 4.0 or 4.1
@item Triggers @tab 4.1
@item Constraints @tab 4.1
@item Cursors @tab 4.1 or 4.2
@item Extensible index types like R-trees @tab R-trees are planned for 4.2
@item Inherited tables @tab Not planned
@end multitable
Other reasons someone may consider for using PostgreSQL:
@itemize @bullet
@itemize @bullet
@item
@item
Standard usage in PostgreSQL is closer to ANSI SQL in some cases.
Standard usage in PostgreSQL is closer to ANSI SQL in some cases.
...
@@ -4993,9 +4970,6 @@ Standard usage in PostgreSQL is closer to ANSI SQL in some cases.
...
@@ -4993,9 +4970,6 @@ Standard usage in PostgreSQL is closer to ANSI SQL in some cases.
@item
@item
One can speed up PostgreSQL by coding things as stored procedures.
One can speed up PostgreSQL by coding things as stored procedures.
@item
For geographical data, R-TREES makes PostgreSQL better than MySQL Server.
@item
@item
The PostgreSQL optimiser can do some optimisation that the current MySQL
The PostgreSQL optimiser can do some optimisation that the current MySQL
optimiser can't do. Most notable is doing joins when you don't have the
optimiser can't do. Most notable is doing joins when you don't have the
...
@@ -14517,7 +14491,7 @@ large systems. You can copy @file{my-xxxx.cnf} to your home directory
...
@@ -14517,7 +14491,7 @@ large systems. You can copy @file{my-xxxx.cnf} to your home directory
All MySQL clients that support option files support the
All MySQL clients that support option files support the
following options:
following options:
@multitable @columnfractions .45 .
6
5
@multitable @columnfractions .45 .
5
5
@item @strong{Option} @tab @strong{Description}
@item @strong{Option} @tab @strong{Description}
@item --no-defaults @tab Don't read any option files.
@item --no-defaults @tab Don't read any option files.
@item --print-defaults @tab Print the program name and all options that it will get.
@item --print-defaults @tab Print the program name and all options that it will get.
...
@@ -36403,7 +36377,7 @@ Transactional @code{InnoDB} tables that have been changed will be invalidated
...
@@ -36403,7 +36377,7 @@ Transactional @code{InnoDB} tables that have been changed will be invalidated
when a @code{COMMIT} is performed.
when a @code{COMMIT} is performed.
A query cannot be cached if it contains one of the functions:
A query cannot be cached if it contains one of the functions:
@multitable @columnfractions .25 .
30 .25 .3
5
@multitable @columnfractions .25 .
25 .25 .2
5
@item @strong{Function} @tab @strong{Function}
@item @strong{Function} @tab @strong{Function}
@tab @strong{Function} @tab @strong{Function}
@tab @strong{Function} @tab @strong{Function}
@item @code{User Defined Functions} @tab @code{CONNECTION_ID}
@item @code{User Defined Functions} @tab @code{CONNECTION_ID}
...
@@ -36416,7 +36390,8 @@ A query cannot be cached if it contains one of the functions:
...
@@ -36416,7 +36390,8 @@ A query cannot be cached if it contains one of the functions:
@tab @code{DATABASE} @tab @code{ENCRYPT} (with one parameter)
@tab @code{DATABASE} @tab @code{ENCRYPT} (with one parameter)
@item @code{LAST_INSERT_ID} @tab @code{RAND}
@item @code{LAST_INSERT_ID} @tab @code{RAND}
@tab @code{UNIX_TIMESTAMP} (without parameters) @tab @code{USER}
@tab @code{UNIX_TIMESTAMP} (without parameters) @tab @code{USER}
@item @code{BENCHMARK}
@item @code{BENCHMARK} @tab
@tab @tab
@end multitable
@end multitable
Nor can a query be cached if it contains user variables,
Nor can a query be cached if it contains user variables,
...
@@ -40496,7 +40471,7 @@ the @code{[Servername]} section of an @code{ODBC.INI} file or
...
@@ -40496,7 +40471,7 @@ the @code{[Servername]} section of an @code{ODBC.INI} file or
through the @code{InConnectionString} argument in the
through the @code{InConnectionString} argument in the
@code{SQLDriverConnect()} call.
@code{SQLDriverConnect()} call.
@multitable @columnfractions .15 .2
5
.65
@multitable @columnfractions .15 .2
0
.65
@item @strong{Parameter} @tab @strong{Default value} @tab @strong{Comment}
@item @strong{Parameter} @tab @strong{Default value} @tab @strong{Comment}
@item user @tab ODBC (on Windows) @tab The username used to connect to MySQL.
@item user @tab ODBC (on Windows) @tab The username used to connect to MySQL.
@item server @tab localhost @tab The hostname of the MySQL server.
@item server @tab localhost @tab The hostname of the MySQL server.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment