|
|
|
MySQL Errors in Latest 0.5.0 Unstable
|
|
|
 |
|
Posted under Development by Kenji on Wednesday February 14 2001 @ 09:23PM EST
Any ideas about what would cause the following errors. Everything is setup properly - running on PHP4 and BSDI.
Warning: 0 is not a MySQL result index in include/common.inc.php on line 704
Warning: fopen("/usr/local/etc/httpd/www/phpweblog/backend/layouts/.xlay","r") - No such file or directory in /usr/local/etc/httpd/www/phpweblog/include/layout.inc.php on line 344
Warning: Cannot add header information - headers already sent in include/common.inc.php on line 384
Warning: 0 is not a MySQL result index in include/common.inc.php on line 98
1
Warning: 0 is not a MySQL result index in /usr/local/etc/httpd/www/phpweblog/include/blocks.inc.php on line 46
Warning: 0 is not a MySQL result index in include/common.inc.php on line 98
Warning: 0 is not a MySQL result index in /usr/local/etc/httpd/www/phpweblog/stories.php on line 88
Warning: 0 is not a MySQL result index in include/common.inc.php on line 159
1
Warning: 0 is not a MySQL result index in /usr/local/etc/httpd/www/phpweblog/include/blocks.inc.php on line 46
Warning: 0 is not a MySQL result index in include/common.inc.php on line 98
1
|
 mochaexpress writes on Thursday February 15 2001 @ 12:45PM EST: [ reply | parent ]
get to the mysql prompt and do:
select * from T_Config;
what do you get? most of the time, it's the Layout. If for some reason when you export your layout and something weird happend and the file got corrupted or if you edit it manually and made an error in there.
try:
UPDATE T_Config SET Value='blurb' where Name='Layout';
and load the page again.
|
kenji writes on Thursday February 15 2001 @ 04:55PM EST: [ reply | parent ]
Thanks for the info. I actually figured out what the problem was. I do development sometimes on my laptop which is running Windows 2000 Pro. Well, I dumped the database using mysqldump and proceeded to then restore the database on another server which happens to be running FreeBSD 4.2. It seems that the windows version of the MySQL mysqldump command has the nasty habit of writing all the table names in lowercase (i.e., t_links, t_config, etc.) which causes the above errors. After I hand edited all the table names to their proper cases, everything worked fine. So if anybody is doing development on a windows machine, you should watch out for this if you move databases to other servers using this backup method. The windows version of MySQL is not case sensitive. Go figure. I have to install Linux or FreeBSD on my laptop. If anybody is interested the version I use of MySQL is 3.23.28-gamma and the mysqldump version is 8.11.
|
|
mochaexpress writes on Thursday February 15 2001 @ 05:33PM EST: [ reply | parent ]
i encountered the same thing but while doing my Database Independent conversions. quotes matter, and also case sensitivity. i just put everything in lowercase.. and that was a bundle of headaches too. but all is good now.
|
|
xdaniel writes on Sunday February 18 2001 @ 01:50AM EST: [ reply | parent ]
Hi, I had the same problem transferring from Win ME to Linux.
|
|
|
|
