Hello. If you have all inserts and updates on the tables from which you've lost your data, you can simply recover the whole database from the binary logs, however if the logs were create later than tables, most probably you won't get the consistent data in them. Use --stop-datetime option for mysqlbinlog utility. See: http://dev.mysql.com/doc/refman/5.0/en/mysqlbinlog.html
Rob Gormley wrote: > Am hoping someone can give me the safest advice here. > > Using 4.1 and InnoDB, someone in an attempt to be helpful set up a lot > of foreign key constraints. However... > > ON DELETE CASCADE > > When we needed RESTRICT. > > Net effect? Some editing today lead to cries of "Where has half the data > gone?" > > We have the binlog, and know the point at which the erroneous stuff > happened - however, no backup exists, so I can't roll forward from that > (don't ask)... > > Is it at all possible to rollback using the binlog to that point? Or is > it time to get back to manual data entry? > > Any help greatly appreciated. > > Rob -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
