#9 Database error

[Kris Stark]

Is there any way to get a log of the SQL transactions between OI and MySQL? For some odd reason, two separate installs have suddenly started to complain that there is no 'customer_telephone' field in the database, when it most definitely does exist on the MySQL database...

Something somewhere is acting squirly, since I have a copy of the production database on a different machine, and connections to that work fine, but on our production server the error pops up regardless of anything. I have tried to use the name of a different, existing field in OI for that (customers_fax) just to see if that would make any difference, but the same error keeps happening.

I can connect to the DB from the same machine which has OI installed on it using the same credentials, and select data from that database and table without issue...

I'm very confused at this stage...

Thanks!

Kris

[Nathan Arendt]

Logged In: YES
user_id=44461
Originator: NO

the field in a normal osCommerce install should be customers_telephone. You should double check your field names and ensure it says customers_telephone.

[Nathan Arendt]

Logged In: YES
user_id=44461
Originator: NO

Or if your database field is customer_telephone you need to change the field name under options from customers_telephone to customer_telephone

[Kris Stark]

Logged In: YES
user_id=681497
Originator: YES

That's just it... The field names do match, and I've been able to query the database directly with the same credentials for the same database field using MySQL Query Administrator from the same remote location.

Further, this install *did* work previously, and was able to make connections, download orders etc. Nothing changed on the OSc side that I can tell - certainly nothing that I did, and the OSc install works perfectly.

The only issue that I had with the system prior to this oddball error was that I was not able to process "all transactions" for shipping w/Endicia - I had to process each one individually...

So, basically I'm trying to trace the SQL call to try and figure out why it is coming back with an erroneous error about the field....

Kris