Backups SQL file is truncated at 40MB??

[MrBaseball34]

I'm trying to upgrade a shop but first I want to place it in a separate directory online.
Note: I had a local version of my old shop and ran the upgrade on it locally.

So, I went to do my DB backup of my development version (1.3.1)
and it creates the backup (all tables) but with one exception.

It truncates the SQL file at around 1,542,000 lines, about 40MB.

I MUST have connections and statistics. I have 24,000 items in my current store and this will
be a HUGE problem when trying to move data to a new DB.

Why is this a limitation in the backup process? Isn't it supposed to work with DB's of any size?
Has anyone else noted this happening?

[tomerg3]

Try exporting the db from phpMyAdmin

[MrBaseball34]

Well, DUH...of course I did it in phpMyAdmin.

I am pointing out a BUG in PS and was wondering why it is limited in such a manner?

I guess it has to be according to your server confiuration because the Backup class
does not use mysqldump to create the file, it does it on the fly with SQL code.

Shame, shame, shame...

[rocky]

You may be interested to know that the Backup tab in PrestaShop was written by someone on these forums, then submitted to PrestaShop, who incorporated it into PrestaShop with a few modifications. I suppose you can blame the PrestaShop for not rewriting the code the right way, but you can't blame them for writing bad code to begin with.

[MrBaseball34]

Well, I was unaware of that fact but it should be in their best interests to fix this problem because I see it as a bug.
There are many store out there that would have backups >40MB and heaven forbid one of them goes down with a faulty backup...