|
|||
|
|||||||||
|
|
|||||||||
 |
 |
 |
 |
|
 |
 |
|||||||||
 |
 |
 |
|||||||||||||
 |
|
|
 |
||||||||||||
 |
 |
||||||||||||||
|
|||||||||||||||
 |
 |
 |
 |
 |
|||||||||||
 |
 |
 |
 |
 |
 |
||||||||||
| OK | Lillibet Layne - Mar 7th, 2005 at 10:05 pm |
| Perfect time to come see what's up on the site. Why do comments not break it? |
| SQL | fatty - Mar 8th, 2005 at 7:38 am |
You're still using mysql, right? If so, you could use the mysqldump program to back up your data. It comes with mysql and if it's not in your path, it should be in the mysql/bin directory. (Ignore all this if you know about it, obviously....). It outputs your data as SQL statements, so you can just pipe it to a file if it's small, or through gzip if it's big. You can do this:mysqldump <database> -u <username> -p | gzip > backup.sql.gz
You can skip the -p if you don't have a password and the -u if you are logged in as the same user you want to use for mysql. Then, if you ever need it back, you do this (you can load it into a different database too, if you need...you just have to do CREATE DATABASE <database>): gunzip -c backup.sql.gz | mysql -u <username> -p <database>The -c tells gunzip to leave the backup there and output to STDOUT so that you can pipe it to mysql and not destroy your backup. So if you knew about that, I'm sorry I blathered on for so long, but if you didn't, now you don't have to worry quite as much about accidently screwing up all of your entries. Sorry it's broken! I must say, it's pretty huge of you to be putting new entries in on the command line...I don't know what your table setup is like, but just the text, title, and date that are visible look like quite a pain in the butt to type out in an SQL statement (especially having to remember to quote everything the right way in all of your sentences). Good luck getting it fixed, and have a good day! |
| Way ahead of you, bud | Matt - Mar 8th, 2005 at 1:33 pm |
| Fatty: I nightly dump it and back it up offsite, so at the most it would be an inconvenience. Just the same, though, writing into SQL by hand is a crazy pain. Lillibet: Comments were the third thing I fixed (behind being able to read old entries, and the ability to view the icons). |
| sorry | fatty - Mar 9th, 2005 at 6:58 am |
| OK, then. Sorry! I didn't mean to go off on a huge tangent about stuff you already knew. I thought you'd know, but then I wasn't sure when you said it was dangerous to enter stuff through command line SQL because you could lose everything. Do you mind my asking what happened that all your SQL statements broke? If you don't want to get into it, that's fine...I'm just a curious, not creepy guy, so I just wondered. |
| The link | Ron - Mar 9th, 2005 at 6:01 pm |
| Free publicity! Sweet! Now I guess I'll have to start updating. |
