Re: Unknown column
Re: Unknown column
- Subject: Re: Unknown column
- From: Ângelo Andrade Cirino <email@hidden>
- Date: Thu, 13 Sep 2012 18:12:20 -0300
Hi Ted,
Good point. In my case the error log is clean:
120913 8:51:45 InnoDB: highest supported file format is Barracuda.
120913 8:51:45 InnoDB: Waiting for the background threads to start
120913 8:51:46 InnoDB: 1.1.8 started; log sequence number 690698052
120913 8:51:50 [Note] Server hostname (bind-address): '(null)'; port: 3306
120913 8:51:50 [Note] - '(null)' resolves to '0.0.0.0';
120913 8:51:50 [Note] - '(null)' resolves to '::';
120913 8:51:50 [Note] Server socket created on IP: '0.0.0.0'.
120913 8:51:50 [Note] Event Scheduler: Loaded 0 events
120913 8:51:50 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.5.24-log' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Server (GPL)
It seems now that the connection is working again, but since I am having other problem with the application and debugging it led me to nowhere, I decided to start a new project and copy file by file to see what happens.
Angelo
Em 13/09/2012, às 18:03, Theodore Petrosky escreveu:
> When I have a problem 'like this' I watch the log files of the database I believe to be talking to. Is there ANY possibility that your WO app is talking to a different backend instance?
>
> if you run your app talking to database1, and database1's logs don't show the error, you are not talking to the database you thought you were talking to.
>
> Ted
>
> --- On Thu, 9/13/12, Ângelo Andrade Cirino <email@hidden> wrote:
>
>> From: Ângelo Andrade Cirino <email@hidden>
>> Subject: Re: Unknown column
>> To: "Johann Werner" <email@hidden>, "Theodore Petrosky" <email@hidden>
>> Cc: "email@hidden Development" <email@hidden>
>> Date: Thursday, September 13, 2012, 4:58 PM
>> Hi Johan and Ted,
>>
>> I had tried this approach too. I copied the generated SQL
>> and used it to perform a query in MySQLWorkBench and the SQL
>> was legal, returned the expected result.
>>
>> There is a new post where I reported that the error is gone,
>> but the Main component is missing :-(
>>
>> Angelo
>>
>> Em 13/09/2012, às 17:51, Johann Werner escreveu:
>>
>>> Have you tried to copy the SQL string from the log and
>> to run it directly in MySQL? Does MySQL report a
>> different/more precise error message? If it returns a
>> correct result there the error lies within WO otherwise your
>> DB/config has to be checked.
>>>
>>
>>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden