JoomlaPlug!

I apologize for a newbie question...

I have noticed that the clones I have made automatically using a cron process have "no drop" in the file name. However, the ones I manually do have "drop" in the file name. I suspect it has to with whether or not "Drop Syntax" is checked.

My question: What is drop syntax? And what are the advantages/disadvantages in using one vs. the other?

Thanks in advance,
Bob

The drop syntax is used in the mysql importing, when importing each table and if the drop syntax is enabled, then we will drop any original table(with same name) and insert the new one instead!

Ovidiu

That makes sense.

If I am making clones for backup purposes--using the clone to restore a corrupted site--would it be best to drop all the tables and have the clone restore them? Or is it best to use the no-drop sequence? I wuold suspect that if I am worried about a corrupted database, I would want to drop the tables and restore it from the clone. But maybe I am wrong.

Is there an advantage of dropping vs. not dropping the tables when restoring a site?

B.

The advantage with dropping is as you said, it will not give you a corrupt result if old tables were already in place!

A drop mysql dump will assure you of an full restore without problems!

Ovidiu

Thanks Ovidiu...now I have one more question: How do I get the drop syntax into a clone that is created by a crontab job. I have a cron job that initiates a twice a week creation of a clone. However, all these clones are no-drop clones. However, any clone I create manually have the drop syntax.

I can only find the setting for drop syntax in the Database options tab when you click on "Create Backup." Is there any way to have the cron backups have the drop syntax?

Bob

Good point, i think we forgot to implement that! Please give us a few days to add that up in the new release! Will send you a post here when it's ready!

Sorry for the inconvenience!

Ovidiu