mirror/mariadb
1
0
Fork 0
mirror of https://github.com/MariaDB/server.git synced 2025-01-16 12:02:42 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

manual.texi:

Browse source 
chow -> show


Docs/manual.texi:
  Monty: chow -> show
This commit is contained in:
unknown 2000-09-09 15:51:21 +00:00
parent fba1498ca0
commit 7babfeb000
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
Docs/manual.texi
View file

@ -28413,18 +28413,18 @@ aren't specified. Another way to around this bug is to upgrade to
MyODBC 2.50.33 and @strong{MySQL} 3.23.x, which together provides a
workaround for this bug!
@item
Set the `Return matching rows' MyODBC option field when connecting to
Set the ``Return matching rows'' MyODBC option field when connecting to
@strong{MySQL}.
@item
You should have a primary key in the table; If not, new or updated rows
may chow up as @code{#Deleted#}.
may show up as @code{#Deleted#}.
@item
You should have a timestamp in all tables you want to be able to update.
For maximum portability @code{TIMESTAMP(14)} or simple @code{TIMESTAMP}
is recommended instead of other @code{TIMESTAMP(X)} variations.
@item
Only use double float fields. Access fails when comparing with single floats.
The symptom usually is that new or updated rows may chow up as @code{#Deleted#}
The symptom usually is that new or updated rows may show up as @code{#Deleted#}
or that you can't find or update rows.
@item
If you still get the error @code{Another user has changed your data} after