Forum Replies Created
-
AuthorPosts
-
minboostMember
Well, I did this at another location so I am not able to check up on it.
However, today I tried it at the office. The phpMyAdmin is version 2.7.0-pl2 and it connects to MySQL 4.0.24. The MySQL version I'm running on my local machine is 4.1.x.
This time it worked fine.
Now I'm not certain about what settings I used to create the SQL dump from phpMyAdmin. I will have to try out the different options to see if I can duplicate the problem again.
Also, I originally misstated the facts in my original post. The records that were being returned from the Yog query window were NOT originally there. Here are the real facts (sorry, I had forgetten them until now):
1. I uploaded the database using an SQL dump from Yog 4.x to phpMyAdmin. The tbl_product containted 3 records.
2. Using a custom ASP backend program, a couple hundred records were added to the table.
3. I downloaded the database as an SQL dump from phpMyAdmin. I DID NOT use the “drop if exists” statements. Instead, I manually dropped all tables from the local database and just imported from the SQL dump (which only had INSERT statements).
4. The problem described in my original post occurred.
For now, it seems, that my problem is solved since I was able to get it to work at the office I am certain I can get it to work where I need it to.
However, if anyone (peterlaursen) wants me to further investigate and discover the exact source of the problem (and potential bug or incompatibility) just ask and I will.
Thanks.
-
AuthorPosts