Akeeba Solo

Wednesday, 25 January 2017 18:03 CST

ANGIE Restore stops with an error when creating a db view. I have attached a zip file containing:

- The full text the error message
- The original view definition of the view that fails
- The sql file (part2) created by Akeeba containing the problem.

What sticks out to me is that the SQL created to define the view is truncated at the line termination character that the View uses as a groupconcat delimiter.
Notice how the .sql file is missing the second half of the view definition. The empty create procedure statement afterwards also seem suspect.

Thursday, 26 January 2017 07:25 CST

nicholas

This is the first time we see that after ten years and million of backups. Unfortunately this is such a rare occurrence that I cannot justify spending the time to find our what is causing it and see if it's something I can fix. If it's a show stopper for you I would rather give you a refund for an unfixable issue per our ToS. Please let me know.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Thursday, 26 January 2017 10:52 CST

[email protected]

There is no need for any discussion about refunds. I am using Akeeba on four systems and (since the 2.0.4 fixes) it works great on 3 of them. It's a good product and you give great support.

I also appreciate that this is an edge case that is probably not worth addressing (although please keep it in the back of your mind).

I should be able work around this by excluding the view. I tried excluding it yesterday and failed (it was still in the backup). It is in a secondary database which has no prefix. Any advice on that?

Thursday, 26 January 2017 20:15 CST

[email protected]

Just following up on my reply above. I have worked around the problem by changing the offending part of the view from:
GROUP_CONCAT(batch_code SEPARATOR '\n')
to
GROUP_CONCAT(batch_code SEPARATOR '<br>')
Just documenting this for the very unlikely event that someone else hits this issue.

Friday, 27 January 2017 07:49 CST

nicholas

I (re-)tried today the VIEW with the line separator string in its definition. It seems that it doesn't throw off just Akeeba Backup but many other database management tools, too. It looks like when we ask MySQL to return the definition of the view it returns the newline as a single newline character instead of escaped (as you'd reasonably expect it to). All tools I've tried failed to export the VIEW correctly. I have not tried mysqldump or MySQL Workbench yet.

Out of curiosity, which software are you using to export and re-import this VIEW? Or are you NOT exporting the VIEW but working from a definition you've stored in your own SQL files?

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Sunday, 26 February 2017 17:17 CST

System Task

system

This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.

Edited by on 2017-02-26 17:17 CST

Support

#26972 Restore fails on a database view containing a line terminator

This is a public ticket

Environment Information