Hi,
I've a doubt about the backup method to dump a mysql database.
I've tried to dump a database using "Sql export" on Phpmyadmin
interface and the resulting file size is 1.031 KB.
I've also tried a dump with:

mysqldump -u root -ppassword --databases dbname > destination

and the resulting file size is about 900 Kb.
My question is:
are there some lost data using mysqldump instead of export on
Phpmyadmin?
Are there some other options to include in mysqldump for a complete
dump?
Thank you so much.

--

Remigio

www.sacraspina.it
www.amicitosondoro.it
www.icmonteodorisio.it
www.giovanichietivasto.it
www.parrocchiacupello.it
www.cralnuovainiziativa.it
www.associazionehistonium.it

remigio:


Please, compare the INSERT statements in both files. I assume, that
their styles are different (e.g. with or without field name list).
In phpMyAdmin, you can switch several styles on or off.


--
Erick

On 24 Giu, 09:53, "Erick T. Barkhuis" <erick.use-... (AT) ardane (DOT) c.o.m>
wrote:
It means that it's the same thing using one of the two methods?
Thanks.

remigio:

Both backups will contain all data. The generated INSERTs are
differently written.
So yes, you can use both files and, upon restore, the table contents
will be as backed up.

Technically, it's not "the same thing", but both methods will lead to
the same result.


--
Erick

"remigio" <linoreale (AT) gmail (DOT) com> wrote

Your Phpmyadmin sql export dump, should that be 1.031MB rather than KB? (If
it were KB then 1.031KB vs 900KB would indicate a serious problem with the
sql export in phpmyadmin.)

I don't use PHP so haven't used Phpmyadmin, but I fully trust mysqldump and
would expect the sql export from phpmyadmin to be as good.

Why not test it and restore both to different and new databases and you can
then run some sql to check that the data in both is the same. But (like
Erick has indicated) I think you'll just be chasing the fact that they both
structure the backup file slightly differently and that that is what
accounts for the difference in size.
--
Brian Cryer
http://www.cryer.co.uk/brian

Brian Cryer:

The dot is most likely not a decimal point. It's a thousands separator,
for which some still use a silly comma.
(But I'm pretty sure you were aware of this)


Sounds like a good idea.

--
Erick

Brian Cryer:

The dot is most likely not a decimal point. It's a thousands separator,
for which some still use a silly comma.
(But I'm pretty sure you were aware of this)


Sounds like a good idea.
Perhaps even better yet: also check the number of records and the size
statistics for each table after restore (using phpMyAdmin, which offers
such info at first glance). They should be the same in both versions.

--
Erick

On 24 Giu, 11:25, "Brian Cryer" <not.here@localhost> wrote:
Thanks.

On 24 Giu, 10:46, "Erick T. Barkhuis" <erick.use-... (AT) ardane (DOT) c.o.m>
wrote:
Thank you.

"Erick T. Barkhuis" <erick.use-net (AT) ardane (DOT) c.o.m> wrote

I wasn't aware or I wouldn't have posted - but in retrospect you are right,
it seems logical that it is being used as a thousands separator here (and I
should have guessed it). I disagree about the comma being silly - to use a
dot as a thousands separator is ambiguous as it means you end up guessing
whether its a decimal point or not ... but I don't want to start an
off-topic debateon this and its probably a discussion for alt.english.usage
rather than comp.databases.mysql and may depend simply on your locale.
--
Brian Cryer
http://www.cryer.co.uk/brian