On Mar 14, 2012, at 11:47 PM, Ramsey Gurley wrote:
>
> On Mar 13, 2012, at 10:08 PM, David Avendasora wrote:
>
>>
>> On Mar 13, 2012, at 8:13 AM, Chuck Hill wrote:
>>
>>> It looks like the problem is the join table. Where does that sit? I
>>> suspect that Propogate Primary Key is not going
On Mar 13, 2012, at 10:08 PM, David Avendasora wrote:
>
> On Mar 13, 2012, at 8:13 AM, Chuck Hill wrote:
>
>> It looks like the problem is the join table. Where does that sit? I
>> suspect that Propogate Primary Key is not going to work across databases.
>> You might have to manage that man
On 2012-03-13, at 10:08 PM, David Avendasora wrote:
>
> On Mar 13, 2012, at 8:13 AM, Chuck Hill wrote:
>
>> It looks like the problem is the join table. Where does that sit? I
>> suspect that Propogate Primary Key is not going to work across databases.
>> You might have to manage that manua
Hello Dave, Chuck, Alex
I guess we would settle to mix them tables in 1 user.
Thanks for the help everybody! I appreciate it.
Troy
On 3/14/2012 1:08 PM, David Avendasora wrote:
On Mar 13, 2012, at 8:13 AM, Chuck Hill wrote:
It looks like the problem is the join table. Where does that sit?
On Mar 13, 2012, at 8:13 AM, Chuck Hill wrote:
> It looks like the problem is the join table. Where does that sit? I suspect
> that Propogate Primary Key is not going to work across databases. You might
> have to manage that manually.
>
> Chuck
Is this where I put my rant about the evils of
2012/3/13 Troy Lumasag
> Hello Alexis,
>
> Thank you.
>
> cross models flattened many-to-many relationships with differents users
> are buggy in my experience.
> You should use the same user in all your connection dictionnaries, easely
> done with Wonder in your Properties :
>
> It needs to use
It looks like the problem is the join table. Where does that sit? I suspect
that Propogate Primary Key is not going to work across databases. You might
have to manage that manually.
Chuck
On 2012-03-12, at 4:56 PM, Troy Lumasag wrote:
> Hello Alexis,
>
> Thank you.
>> cross models flatten
Hello Alexis,
Thank you.
cross models flattened many-to-many relationships with
differents users are buggy in my experience.
You should use the same user in all your connection dictionnaries,
easely done with Wonder in your Properties :
It needs
Hello Fabian,
Many thanks for your quick reply but I already had the Plugin
specified in my Model.
On 3/12/2012 6:37 PM, Fabian Peters wrote:
Hello Troy,
Am 12.03.2012 um 10:58 schrieb Troy Lumasag:
Hello everyone,
Hi,
cross models flattened many-to-many relationships with differents users are
buggy in my experience.
You should use the same user in all your connection dictionnaries, easely
done with Wonder in your Properties :
dbConnectURLGLOBAL = jdbc:oracle:thin:@db.test:1521:oracletest
dbConnectUserGLOBA
Hello Troy,Am 12.03.2012 um 10:58 schrieb Troy Lumasag:Hello everyone,I'm new to Webobjects and Wonder and I enjoy it a lot. I'm having a simple insert problem.Welcome!My DB is Oracle and I have 2 Models(different User) .My EOModel would look like this:Model1 URL: jdbc:oracle:thin:@db.test:1521
Hello everyone,
I'm new to Webobjects and Wonder and I enjoy it a lot. I'm having a
simple insert problem.
My DB is Oracle and I have 2 Models(different User) .
My EOModel would look like this:
*Model1*
URL: jdbc:oracle:thin:@db.test:1521:oracletest
user:OracleConnect
*Model2*
UR
12 matches
Mail list logo
