(ok 2.11.3) Error importing file with lowercase \"delimiter\"

Logged In: YES
user_id=1383652
Originator: NO

if I remember correctly "delimiter |;" only works in the CLI
(that's why the sql window needs an extra delimiter input field).

Logged In: YES
user_id=1914403
Originator: YES

Shouldn't a web interface provide the same functionality as the CLI when it comes to executing SQL statements?

Logged In: YES
user_id=1383652
Originator: NO

Sorry, I should have explained the procedure.
Here is how to mimic the CLI:

a)
replace the lines

017: "delimiter |" with "/* delimiter |*/"

and

173: "END |" with "END /* | */"

b)
select your target db,
copy and paste the new text into the SQL window.
change "Delimiter [ ; ]" to "Delimiter [ | ]" and Go

Result:
Your SQL query has been executed successfully
Routines
Name Type Return type
BASE64_DECODE
Drop FUNCTION blob
BASE64_ENCODE
Drop FUNCTION blob

see http://pma.cihar.com/trunk-config/?db=1823045base64warforge00
(atm, databases often get deleted)

Logged In: YES
user_id=1383652
Originator: NO

you can export this db with tables and functions :
[ tick this ] Add CREATE PROCEDURE / FUNCTION

(atm only with pma 3.0 successfully, I'll file a separate bug report for pma 2.11.2)

...
and import the dump back successfully (with both pma 2.11.2 and pma 3.0)
see: http://pma.cihar.com/trunk-config/?db=211importFunctionsFrom300
(created by "STABLE" using the pma 3.0 dump)

Logged In: YES
user_id=1383652
Originator: NO

well,
in your summary you talked about "the SQL Query textarea".
I hope I made clear how to execute those statements.

On *IMPORT* there is indeed a pma bug:
"delimiter" is not correctly recognized but if you change it to
"DELIMITER" the file can be imported without problems.

Logged In: YES
user_id=1383652
Originator: NO

btw,
I just read that the export bug will be fixed in pma 2.11.3,
hopefully the "delimiter" (lowercase) issue as well ;)

Logged In: YES
user_id=210714
Originator: NO

Fixed in subversion, thanks for reporting.