Installing 2nd instance on windows.

[C K]

Is it possible to install more than instances on Linux of MySQL 5.0?
I am using WinXP SP 2 and MySQL 5.0.17.
Thanks
CPK

--
Keep your Environment clean and green.

Re: How to limit usage of mysql server's memory/cpu for each databases ?

[B. Keith Murphy]

Halid Faith wrote:

I use mysql4.1.22, php4.4.6 and apache2.0.59.
I want to put an quota for each databases and mysql users. How can I 
do that

mysql will limit each database's memory usage? Because some mysql users
sometimes use much memory while doing a sql query.
Also How can I put an quota for each databases as data size ( like 1 
Mbyte )

?



  

Halid,

I don't think there is any way to do this from within MySQL.  If you 
were ambitious you could implement the datasize quota with some type of 
script.


Hope that helps.

Keith

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

data corruption with mysqldump

[Frames Project]

Hello

I send you this message from the Mediawiki mailing list.
It explains clearly that mysqldump has an incorrect behavior which may
lead to data destruction (I got this problem)

Could you please do something to fix it ?
Thanks

Francois Colonna


-BEGIN of MESSAGE-


Sylvain Machefert wrote:

Hi Brion,
what is strange, is that only the titles are affected, not the content of
the pages. Is that normal ?


Yes -- the page text is in a binary BLOB field, which will not undergo
the bogus lossy conversion.

The summarize, the problem is roughly:

* MediaWiki assumes that MySQL will preserve data that is put into it
* MySQL sometimes corrupts the data

in a little more detail:

* Due to the limitations of MySQL's Unicode support, but default we
continue to treat MySQL fields as binary and store pure UTF-8 Unicode in
them, although MySQL may have them listed as Latin-1 depending on your
server's defaults.

* The mysqldump backup program by default in 4.1 and later applies a
conversion of non-binary fields to UTF-8, with a marker to have them
appropriately converted back when read in.

* This conversion is lossy -- it treats Latin-1 as the Windows-1252 code
page, which is an extension of ISO 8859-1 with additional characters in
the 128-159 range which in ISO 8859 and Unicode is supposed to contain
non-printing control characters. Four of the code points in this range
are not assigned in Windows-1252, and so cannot be converted to UTF-8
Unicode -- these characters are silently corrupted into ? characters
during the conversion if they appear.

* The UTF-8 encoding of Unicode uses the byte values which correspond to
those four non-convertible characters.

* As a result, UTF-8 text in a Latin-1 field may be corrupted, as some
characters are destroyed in the conversion back and forth.

Use the --default-charset=latin1 option on mysqldump when creating your
database dumps to avoid this lossy conversion. (And/or find another way
to dump/copy databases or another equivalent option to avoid the
unnecessary conversion.)

Since it appears that your hosting provider did this for you, you may
need to ask them to redo it. Alternatively, you may be able to rig up a
statistical fix based on which characters are being corrupted, though
I'm not sure how easy that would be.

- -- brion vibber (brion @ wikimedia.org)

--- END of MESSAGE
-

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]