What not to do in mysql
Aug. 19th, 2002 11:49 am![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
annathepiperTell it, "delete from timeline where id>1-64" where what you actually MEAN is "delete from timeline where id>1064". Because this apparently translates to "delete EVERYTHING"!
And if you do do that, for gods' sake, don't actually close the mysql session, because then all your transactions will then be made final and you don't have a chance to undo what you just did to completely hose yourself and have to enter over a thousand records of data all over again.
ARGH!
And if you do do that, for gods' sake, don't actually close the mysql session, because then all your transactions will then be made final and you don't have a chance to undo what you just did to completely hose yourself and have to enter over a thousand records of data all over again.
ARGH!
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
EEP
Date: 2002-08-19 12:16 pm (UTC)(IT would make sense that, in a database with no negative/0 IDs, id> (1-64) would be interpreted as everything)
Where is the data currently? Anyway way of just importing instead of typing in manually?
Re: EEP
Date: 2002-08-19 01:53 pm (UTC)The original form of the data is a bunch of straight HTML files that I have been manually converting to table format to read into the database. So I haven't really totally lost the data, but I will have to convert it again. Grf.