Recent changes to bugs

UTF8 content bug on Intel with 0.7b5

Tobias Munk — Wed, 20 Aug 2008 14:21:03 -0000

Hi,

we ran into a really weird bug, confirmed with OS X 10.4 and 10.5.

I am running 0.7b5 on a MacBook Pro (Intel).
I set my default encoding to UTF8.

Now when I start CocoaMySQL and select a table which has special chars in certain fields. In my example here: Ø or 'Ø'.
I see only "NULL" values for the corresponding fields. And also when changing a value in the row. The field containing a special char will be overwritten with "NULL" - very bad :(

This bug does not occur when reselecting UTF8 from the lower left dropdown. I also found out that Macs with PPC processor do not have this bug. And last but not least this bug does not exist in 0.7b4.

Best regards,
schmunk.

PS: Tested with MySQL 5.

text to hex ???

pcb_nl — Sat, 31 Mar 2007 12:53:38 -0000

i used CocoaMySQL-v0.7b4

a simple tabel

CREATE TABLE project (
project varchar(50) NOT NULL default '',
jaar year(4) default NULL,
opmerkingen blob,
PRIMARY KEY (project)
) TYPE=MyISAM;

INSERT INTO project VALUES ('Twijnstra & Gudde wandschildering', '2004', 'De wandschildering in het hoofdkantoor van Twijnstra & Gudde te Amersfoort.');

after viewing contents of 'opmerkingen' the text change into

44652077616E64736368696C646572696E6720696E2068657420686F6F66646B616E746F6F722076616E205477696A6E73747261202620477564646520746520416D657273666F6F72742E

this looks like hexadecimal.

i changed the data-type into text and now it works correct.

version 0.5 (v0.5) did not have this problem

thanks,
piet

Unintended Decimal Field Update

zarac — Mon, 08 Jan 2007 20:03:06 -0000

When editing another field in a record containing a decimal field, the decimal field value is changed.

The command below was executed when I updated only the invoice_id field; the amount was correctly showing as 75.00 before the update and incorrectly as 99999999.99 after the update. The value in the database table is now incorrect.

/* MySQL 12:52:38 */ UPDATE `items` SET `id`='14', `transact_id`='100000', `account_id`='1216', `cleared_enum`='2', `amount`='37352E3030', `account_name`='Kerns', `date`='1999-01-01', `description`='Annual Assessment', `year`='1999', `notes`='', `invoice_id`='14' WHERE `id` = '14';

No search operators for decimal fields

zarac — Mon, 08 Jan 2007 19:22:53 -0000

After choosing a decimal field in the seach field popup, there are no options available in the search operators popup. Version 0.7b5.

Memory hole and crash during mysql dumps

Kristofer Widholm — Thu, 21 Sep 2006 00:47:57 -0000

Hi, I just posted this to macupdate.com, and then
thought it was better to put it where it belongs: in
the bug channel!

Still my favorite graphical interface to MySQL
databases. Thanks to the developers for their work.

I still have one MAJOR flaw to point out. Do a MySQL
table dump with drop tables on even a medium sized
database (50,000 rows, four tables), and prepared to
see CocoaMySQL hang (reports 101% processor usage and
becomes unresponsive and gobbles up massive amounts of
RAM until you force quit it).

This behavior has been verified on three different Macs
(PowerPC and Intel) with different OS versions since at
least the 0.5 days in CocoaMySQL, and it still exists!

I love CocoaMySQL, but am sad that I still need to use
the command line for any data lifting of substance.

Suggestion: Feed the mysqldump to a shell subprocess
and just let it notify the application when it is done.
This would free up the user interface in the meantime
and would handle the memory issues.

Steps to reproduce:
1. Connect to any MySQL database (version 3.x, 4.x, or
5.x) of medium size (50,000 rows or thereabouts should
be sufficient).
2. Select File:Export:Cocoa MySQL dump
3. Make sure all tables in the database are selected
(default), and choose "Add drop table".
4. Click OK and watch MySQL start gobble memory and
hang forever in Activity Monitor.

Again, this happens on Panther systems, Tiger systems,
both PowerPC and Intel, and on all databases I've tried
it on as long as there is a table or two of medium size.

On connection 'localhost' fails but '127.0.0.1' suceeds

Chris Parsons — Thu, 10 Aug 2006 14:14:40 -0000

Hi there,

CocoaMySQL appears to ignore a non-standard port when
'localhost' is given as the hostname. Tested on 0.7b4.

To reproduce the problem:

1. Create a new session
2. Setup port forwarding (ssh -L 8888:localhost:3306 ...)
3. Enter 'localhost' and '8888' in your descriptor with
your username and password, and it fails.
4. Change 'localhost' to 127.0.0.1 and it succeeds.

Note that if you're running a local mysql server on
port 3306 it'll still attempt to connect to that if
'localhost' is specified, even if port 8888 is specified.

enum type length display wraps

Anonymous — Mon, 07 Mar 2005 15:02:56 -0000

See attached PDF

Unable to connect to ssh-mapped localhost port

Scott Ellsworth — Tue, 07 Dec 2004 20:59:39 -0000

Hi,

I am very impressed with CocoaMySql. It is very elegant, and
works well.

I have run into one problem. I use ssh to connect to one of my
mysql servers, using a localhost port mapped to the mysql port
inside the client, and it appears that CocoaMySql does not like this.

For example, if I have connected via SSH with a command like:
ssh -l sellswor -c blowfish -g -L13306:sekmet3.company.com:3306
sshhost.company.com

The following command line does connect to the server:

work@phantom:work$ mysql --user=root --
password=whatevermyrootpasswordis --host=localhost --
port=13306

producing

Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 55 to server version: 4.0.18-standard-
log

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> use mysql;
Reading table information for completion of table and column
names
You can turn off this feature to get a quicker startup with -A

mysql> exit
Bye

but the same from cocoamysql does not:

<dict>
<key>database</key>
<string></string>
<key>host</key>
<string>localhost</string>
<key>name</key>
<string>root@sekmet3ssh</string>
<key>port</key>
<string>13306</string>
<key>socket</key>
<string></string>
<key>user</key>
<string>root</string>
</dict>

Could it be that the localhost address is making it ignore the port?

I have also tried 127.0.0.1 as the address, and it did not seem to
make a difference.

(NB: the company names, account names, and passwords are all
faked, but the terminal output was copied from my terminal
window.)

Cannot set "NOT NULL" without setting a default value

Anonymous — Fri, 26 Nov 2004 23:15:57 -0000

CocoaMysql fails adding a row if I set it to NOT NULL
without specifying a default value. I don't want a
default value - it should fail runtime if the
application does not provide a value.

Connecting to a MySQL 4.1.x server

Ryan Schmidt — Thu, 04 Nov 2004 14:01:48 -0000

It seems that CocoaMySQL 0.5 cannot connect to a MySQL 4.1.x
server unless that server is using the old password storage
mechanism. Could CocoaMySQL be updated to use the MySQL 4.1.x
client libraries to eliminate this server-side restriction? Thanks.

The issue was originally discovered in a discussion which can be
viewed here:

http://www.entropy.ch/phpbb2/viewtopic.php?p=6422#6422