Thanks for the suggestion. I'm not sure what you mean when you say I should restore to a file. Do you mean I should
dumpthe database to an SQL file instead of the "compressed" format?
What do you think I will find?
In the database dump, it is including a row that should be marked as deleted. I can select on that key in the
productiondatabase and get zero rows, and I can select on that key in the restored database and find the row. When I
ignoreerrors the data is restored, but the foreign key can't be created (and that is the only error I encounter). The
presenceof the data in the dump can not be contested... :)
--- On Thu, 12/10/09, Adrian Klaver <aklaver@comcast.net> wrote:
>
> One thing that comes to mind is to restore the dump file to
> a file instead of a
> database and see what is being dumped from the live
> database.
>
>
>
> --
> Adrian Klaver
> aklaver@comcast.net
>
