• My installation on windows 98 was working great. it is wordpress 1.2.1 with apache 1.3.38 , php 4.3.8, and mysql 4.0.12.
    I did some stuff earlier today with spybot and adaware to clean up the machine and suddenly after that my post2cat table is hosed. I cant access it from php, from mysql or from phpadmin. the other wordpress tables seem ok, and functions on screens that do not go to post2cat work fine.
    I dont really have that much stuff only 5 categories and only about 60 posts. but of course i didnt back up database. Is there a way i can correct the post2cat table to match up with my other data which seems fine? or otherwise get the system going ok? anyone else have this problem?
    is there any doc on what the post2cat table structure is and how it is used?
    thanks a lot! the pain of no backup!!
    just_bruce

Viewing 1 replies (of 1 total)
  • Thread Starter just_bruce

    (@just_bruce)

    Well after a good night’s sleep i figured out how to fix it. It was a mysql db problem.
    One can use
    mysqlcheck –auto-repair databasename
    to check all tables in a db and repair them.
    works for the 127 error. there were records hosed , probably indexes, in the post2cat and the post tables.
    incidentally, use
    mysqldump -r filename –opt databasename
    to back up database content into a file that can be reloaded. the resulting file is just text and is easy to reload. use the -r switch in windows, not the –tab switch (which is for unix like systems). see mysql doc sec 8.6 (approx) for this!
    can tie off this thread now unless someone has other comments soon. I hope it is helpful to someone. A learning experience for me! Now I will schedule backups.

Viewing 1 replies (of 1 total)
  • The topic ‘mysql error from post2cat table’ is closed to new replies.