p.s. PLEASE can you put a [mysql] tag on the list???
Please not, it wastes space on the screen.
not a lot of space - and does have the great advantage that we
can then filter out the mysql stuff into a separate mailbox whihc
(on standard UNIX mail) isnt possible without it.
-pcf.
You need to create a new user and group for mysql.
Open your OSX manuals and start reading.
Additional hint - nidump and niload will do the trick (assuming
it works like alll other NeXT systems, which it seems to).
-pcf.
-
am running mysql 3.44 at RHL7.2, how can i setup up mysql to store/show
characters of language such as hebrew/arabic?
My best suggestion would be to store all your test in Unicode UTF-8 format
and use the type BLOB in the table in order to store it. We do this
and can quite happily mix
We are discussing the 'mysql' client which is often used to write
scripts that run under the
UNIX shell.
...
If you write a script that has two semi-colons in a row, the second one
is ignored and no error message is given.
Err, not true (in amysql script anyway)
I think you are trying
mysql show databases;
+-+
| Database|
+-+
| CarbonUFSVolumeInfo |
| mnta|
| mntb|
| vi.recover |
+-+
4 rows in set (0.04 sec)
Umm, those look very much like files from a
Yeah, just go with InnoDB. :-)
any good ? I took a look at the documentation, but it all seemed somewhat
heavyweight for my liking...
I have an application that runs very nicely at the moment - we have one minor
problem which is that we have one insert into two tables which may not hapen
If I have amast/salve pair where the slave is replicating from
the master then do the table types have to be the same ?
Specifically can I have a myisam table on the master and replicate to
a bdb table on the slave ?
The reasoning behind this is to try and find a *fast* was to convert
a MYISAM
CREATE TABLE new_table (all like your current one, besides indexes)
TYPE=BDB;
INSERT INTO new_table SELECT * FROM old_table;
CREATE INDEX ... ON new_table;...
ALTER TABLE new_table ADD PRIMARY KEY (...);...
RENAME old_table TO old_table_bak;
RENAME new_table TO old_table;
That should
