Re: creating a second database connection
Re: creating a second database connection
- Subject: Re: creating a second database connection
- From: Tim Worman <email@hidden>
- Date: Thu, 23 Aug 2012 12:32:33 -0700
In my use, I build the cross-database relationship logic manually rather than actually modeling it.
Tim
On Aug 23, 2012, at 11:52 AM, Amedeo Mantica <email@hidden> wrote:
> Theoretically table names could be same. You can have table name different from entity name. Btw there is a bug in wo 5.4.3 that may cause issues in cross database relationship, but for read only should work with no issues.
>
> Amedeo
>
> Sent from my iPhone
>
> On 23/ago/2012, at 20:28, Tim Worman <email@hidden> wrote:
>
>> +1
>>
>> It just works. You simply can't have entities with the same name. I have two different databases as well as JNDI entities.
>>
>> Tim
>> UCLA GSE&IS
>>
>> On Aug 22, 2012, at 9:50 PM, Cheong Hee (Gmail) <email@hidden> wrote:
>>
>>> The simplest way is to create two eomodel and set their connection dictiionary respectively. It will then transparent to you when do fetching.
>>> No worry b'cos it is wo.
>>>
>>> ----- Original Message ----- From: "Theodore Petrosky" <email@hidden>
>>> To: <email@hidden>
>>> Cc: <email@hidden>
>>> Sent: Thursday, August 23, 2012 9:55 AM
>>> Subject: Re: creating a second database connection
>>>
>>>
>>>> I hadn't even thought of JasperReports yet. but, I could probably create a 'special EO', copy the attributes that I want to report on. and print this third EO.
>>>>
>>>> or as you said pass the second EO as a parameter object and use a sub report. i was doing that for my to-many relations.
>>>>
>>>> My issue was I couldn't image how to connect to two different databases at the same time. It appears this is the easier of the difficult parts.
>>>>
>>>>
>>>> Ted
>>>>
>>>> --- On Wed, 8/22/12, email@hidden <email@hidden> wrote:
>>>>
>>>>> From: email@hidden <email@hidden>
>>>>> Subject: Re: creating a second database connection
>>>>> To: "Theodore Petrosky" <email@hidden>
>>>>> Cc: "Amedeo Mantica" <email@hidden>, "Paul Yu" <email@hidden>, "email@hidden" <email@hidden>
>>>>> Date: Wednesday, August 22, 2012, 7:21 PM
>>>>> Jasper Reports? You can't use two
>>>>> data sources in the same report, you will have to use
>>>>> sub-reports.
>>>>>
>>>>> Envoyé de mon iPhone
>>>>>
>>>>> Le 2012-08-22 à 19:19, "Theodore Petrosky" <email@hidden>
>>>>> a écrit :
>>>>>
>>>>>> db two is to read only. I want to munge together a
>>>>> report. I'll try the two models and see how it works out. it
>>>>> just sounds too simple.
>>>>>>
>>>>>> Ted
>>>>>>
>>>>>>
>>>>>> --- On Wed, 8/22/12, Paul Yu <email@hidden>
>>>>> wrote:
>>>>>>
>>>>>>> From: Paul Yu <email@hidden>
>>>>>>> Subject: Re: creating a second database connection
>>>>>>> To: "Amedeo Mantica" <email@hidden>
>>>>>>> Cc: "email@hidden"
>>>>> <email@hidden>
>>>>>>> Date: Wednesday, August 22, 2012, 6:28 PM
>>>>>>> But cross model joins would be an
>>>>>>> issue?
>>>>>>>
>>>>>>> Sent from my iPad
>>>>>>>
>>>>>>> On Aug 22, 2012, at 4:09 PM, Amedeo Mantica <email@hidden>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Just create two eomodels
>>>>>>>>
>>>>>>>> Sent from my iPhone
>>>>>>>>
>>>>>>>> On 22/ago/2012, at 21:55, Theodore Petrosky
>>>>> <email@hidden>
>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> I have an app that captures data on events
>>>>> and
>>>>>>> writes this to my postgresql database.
>>>>>>>>>
>>>>>>>>> I have other data that lives in an Oracle
>>>>> database
>>>>>>> that I need to query to merge with to create a
>>>>> report.
>>>>>>>>>
>>>>>>>>> like (data from PG) + (data from Oracle) =
>>>>>>> myReport.
>>>>>>>>>
>>>>>>>>> I have no experience trying to connect to a
>>>>> second
>>>>>>> database in an app. Are there any examples of doing
>>>>> this?
>>>>>>>>>
>>>>>>>>> Please, I have no idea where to start.
>>>>>>>>>
>>>>>>>>> Ted
>>>>> _______________________________________________
>>>>>>>>> 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
>>>>> _______________________________________________
>>>>>>>> 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
>>>>>>> _______________________________________________
>>>>>>> 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
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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
>>>>
>>>> _______________________________________________
>>>> 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
>>>
>>> _______________________________________________
>>> 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
>>
>>
>> _______________________________________________
>> 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
_______________________________________________
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