Bug#364702: phpmyadmin: Invalid data dump for ascii varchar columns

2006-06-26 Thread Létező
Note: The Debian bug-reporting system has been dropped my message because "too many invalid commands found" in it. I'm resending my message and _not_ Cc:-ing it to [EMAIL PROTECTED] now. Sorry if you got it twic Hi! > The dump is not fully correctly, because the last character in each line is >

Bug#364702: phpmyadmin: Invalid data dump for ascii varchar columns

2006-06-25 Thread Létező
Hi! > The dump is not fully correctly, because the last character in each line is > comma (,), not (;). Yes, it's true. PHPMyAdmin generated the dump this way. The generator code for UPDATEs could be somehow mixed with the extended (multi-record) INSERT statements. Last UPDATE is colsed with a

Bug#364702: phpmyadmin: Invalid data dump for ascii varchar columns

2006-06-25 Thread Piotr Roszatycki
tag 364702 unreproducible moreinfo thanks Hi. The dump is not fully correctly, because the last character in each line is comma (,), not (;). The hexadecimal encoding in place of ascii was correct because you used collate ascii_bin. I've called sed -i s/,$/;' dump.sql and imported your fil

Bug#364702: phpmyadmin: Invalid data dump for ascii varchar columns

2006-04-24 Thread Ferenczi Viktor
Package: phpmyadmin Version: 4:2.8.0.2-4 Severity: normal I've dumped a table as UPDATE commands and got invalid result for the name column. Large hexadecimal numbers are dumped instead of strings. This cannot be executed on the same version of mysql. Dump is useless: -- phpMyAdmin SQL Dump --