[kepler-dev] This is the result if i run postgresql only.

[Daniel Crawl]

Hi Rajan,

What happens if you access only the MySQL database?

Also, only one of dbcon or dbParams needs to be connected
to the Database Query actor. What happens if you only
connect one?

I just created a workflow that queries two different
types of databases, and had no problems. Maybe you
could send me your workflow?

Thanks,


  --dan


Matt Jones wrote:
> My guess is that you have uncovered a bug.  Note that the mysql actor
> is complaining about postgres configuration information, which means
> it is using the wrong configuration data. This is a wild guess, but
> its possible that DBConnection uses some static variables improperly,
> and the order of firing makes a
> difference in which actor fails first (ie, after init is run for both
> actors, fire is run, but for the first actor and then fails because it
> has config data in the static members from
> the second actor).  If you switch the configuration info in  the two
> db connections  (ie., reconfigure the pg connection with mysql
> info and reconfigure the mysql connection with pg info), does the
> postgres actor fail rather than
> the mysql actor? I would expect so if the mysql actor ran first and
> got its config info from the second db config actor.
>
> Matt
>
> On Thu, May 14, 2009 at 8:09 PM, Rajan Saminathan
> <rajan.saminathan at mimos.my> wrote:
>   
>> Dear Sir,
>>
>>
>>
>> This is the result if I run postgresql only.
>>
>>
>>
>>
>>
>>
>>
>> From: ludaesch at gmail.com [mailto:ludaesch at gmail.com] On Behalf Of Bertram
>> Ludaescher
>> Sent: Friday, May 15, 2009 11:47 AM
>> To: Rajan Saminathan
>> Cc: kepler-dev at ecoinformatics.org
>> Subject: Re: [kepler-dev] I am getting error if i connect two different
>> databases. Let me know how two solve this error.
>>
>>
>>
>> Hi Rajan:
>>
>> What happens if you only use the PosgreSQL database: do you also get this
>> error?
>> The error message indicates that you/the workflow has no access to the local
>> Postgres database.
>> This could be the source of the error (just a guess..)
>>
>> Bertram
>>
>> On Thu, May 14, 2009 at 8:47 PM, Rajan Saminathan
>> <rajan.saminathan at mimos.my> wrote:
>>
>> Dear Sir,
>>
>>
>>
>>           I am connecting two following two different databases 1. MySQL  2.
>> PostgreSQL.  While run the workflow I am getting error. Below you can see
>> the error. Any one let me know how to fix this error.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Thanks and Regards,
>>
>>                         Rajan S.
>>
>>
>>
>> ------------------------------------------------------------------
>> -
>> -
>> DISCLAIMER:
>>
>> This e-mail (including any attachments) may contain confidential
>> information.
>> If you are not the intended recipient, you are hereby notified that any
>> dealing,
>> review, distribution, printing, copying or use of this e-mail is
>> strictly prohibited.
>> If you have received this email in error, please notify the sender or
>> MIMOS Berhad
>> immediately and delete the original message. Opinions, conclusions and
>> other
>> information in this e-mail that do not relate to the official business
>> of MIMOS Berhad
>> and/or its subsidiaries shall be understood as neither given nor
>> endorsed by MIMOS
>> Berhad and/or its subsidiaries and neither MIMOS Berhad nor its
>> subsidiaries accepts
>> responsibility for the same. All liability arising from or in connection
>> with computer
>> viruses and/or corrupted e-mails is excluded to the fullest extent
>> permitted by law.
>>
>> _______________________________________________
>> Kepler-dev mailing list
>> Kepler-dev at kepler-project.org
>> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
>>
>>
>>
>> ------------------------------------------------------------------
>> -
>> -
>> DISCLAIMER:
>>
>> This e-mail (including any attachments) may contain confidential
>> information.
>> If you are not the intended recipient, you are hereby notified that any
>> dealing,
>> review, distribution, printing, copying or use of this e-mail is
>> strictly prohibited.
>> If you have received this email in error, please notify the sender or
>> MIMOS Berhad
>> immediately and delete the original message. Opinions, conclusions and
>> other
>> information in this e-mail that do not relate to the official business
>> of MIMOS Berhad
>> and/or its subsidiaries shall be understood as neither given nor
>> endorsed by MIMOS
>> Berhad and/or its subsidiaries and neither MIMOS Berhad nor its
>> subsidiaries accepts
>> responsibility for the same. All liability arising from or in connection
>> with computer
>> viruses and/or corrupted e-mails is excluded to the fullest extent
>> permitted by law.
>>
>> _______________________________________________
>> Kepler-dev mailing list
>> Kepler-dev at kepler-project.org
>> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
>>
>>
>>     
>
>
>
>