You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ojb-user@db.apache.org by David Le Strat <dl...@yahoo.com> on 2004/02/29 09:09:21 UTC

OTM M-N Mapping Issue

Hello there,

I am using OTM with M-N mapping. I am having an issue
with OTM, where OJB violate foreign key constraints.

I have the following mapping:

PREFS_NODE <-- PREFS_NODE_PROPERTY_KEY -->
PREFS_PROPERTY_KEY

With OTM, OJB tries to delete PREFS_PROPERTY_KEY
before removing PREFS_NODE_PROPERTY_KEY therefore
violating foreign key constraint.  Has anybody else
experienced the same behavior.

Regards,

David Le Strat.

__________________________________
Do you Yahoo!?
Get better spam protection with Yahoo! Mail.
http://antispam.yahoo.com/tools

---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-user-help@db.apache.org

Re: [OTM] collection-descriptor issue with latest from head.

Posted by David Le Strat <dl...@yahoo.com>.
Oleg,

I am not sure if one of the patches submitted fixed my
issue, but this is now working with the latest head.

Thanks for your help.

David
--- Oleg Nitz <on...@ukr.net> wrote:
> Hi David,
> 
> Can you give at least a small code snippet, please?
> 
> Regards,
>  Oleg
> 
> On Monday 01 March 2004 15:12, David Le Strat wrote:
> > Hello,
> >
> > I am having the weirdest issue, any suggestion;
> >
> > Basically, I want to add a collection of
> properties to
> > a node.
> >
> > In my test, I have only 1 property:
> >
> > Properties: [[nodeId, 5], [propertyKeyId, 21],
> > [propertyKey,
> >
>
org.apache.jetspeed.prefs.om.impl.PropertyKeyImpl@162d950],
> > [propertyValue, true], [creationDate, 2004-03-01
> > 10:03:14.812], [modifiedDate, 2004-03-01
> > 10:03:14.812]]
> >
> > I open the transaction and do setNodeProperties on
> the
> > node object.
> >
> > The transaction is open, just before committing, I
> > check to see that the properties are set correctly
> on
> > the object:
> >
> > DEBUG:
> org.apache.jetspeed.prefs.impl.PreferencesImpl
> > -
> >
> > Node for update: [[parentNodeId, 4], [nodeName,
> > propertyset1], [fullPath,
> > /user/principal1/propertyset1], [nodeType, 0],
> > [nodeKeys,
> >
>
[org.apache.jetspeed.prefs.om.impl.PropertyKeyImpl@952905,
> >
>
org.apache.jetspeed.prefs.om.impl.PropertyKeyImpl@b83be0,
> >
> org.apache.jetspeed.prefs.om.impl.PropertyKeyImpl@1
> > 631573,
> >
>
org.apache.jetspeed.prefs.om.impl.PropertyKeyImpl@1533c8]],
> > [nodeProperties, [[[nodeId, 5], [propertyKeyId,
> 21],
> > [propertyKey,
> >
>
org.apache.jetspeed.prefs.om.impl.PropertyKeyImpl@162d950],
> > [propertyValue, true], [creationDate, 2004-03-01
> > 10:03:14.812], [modifiedDate, 2004-03-01
> > 10:03:14.812]]]
> > ], [creationDate, 2004-03-01 09:34:13.138],
> > [modifiedDate, 2004-03-01 10:03:14.812]]
> >
> >
> > As you can see [nodeProperties,...] is set, I also
> > change the [modifiedDate, ...].
> >
> > When I close the transaction, I get
> [nodeProperties,
> > []]: the nodeProperties collection is gone...
> >
> > But [modifiedDate, 2004-03-01 10:03:14.802] is
> still
> > there.
> >
> > I can't think of anything that would cause this
> > behavior.  Any help is appreciated.
> >
> >
> > DEBUG:
> > org.apache.ojb.broker.accesslayer.JdbcAccessImpl -
> > executeUpdate : [[parentNodeId, 4], [nodeName,
> > propertyset1], [fullPath,
> > /user/principal1/propertyset1], [nodeType, 0],
> > [nodeKeys,
> >
>
[org.apache.jetspeed.prefs.om.impl.PropertyKeyImpl@162d950,
> >
> org.apache.jetspeed.prefs.om.impl.PropertyKeyImpl@a
> > 937cd,
> >
>
org.apache.jetspeed.prefs.om.impl.PropertyKeyImpl@18e899c,
> >
>
org.apache.jetspeed.prefs.om.impl.PropertyKeyImpl@ec8784]],
> > [nodeProperties, []], [creationDate, 2004-03-01
> > 09:34:13.138], [modifiedDate, 2004-03-01
> > 10:03:14.802]]
> > DEBUG:
> > org.apache.ojb.broker.accesslayer.JdbcAccessImpl -
> > executeUpdate : [[parentNodeId, 4], [nodeName,
> > propertyset1], [fullPath,
> > /user/principal1/propertyset1], [nodeType, 0],
> > [nodeKeys,
> >
>
[org.apache.jetspeed.prefs.om.impl.PropertyKeyImpl@162d950,
> >
> org.apache.jetspeed.prefs.om.impl.PropertyKeyImpl@a
> > 937cd,
> >
>
org.apache.jetspeed.prefs.om.impl.PropertyKeyImpl@18e899c,
> >
>
org.apache.jetspeed.prefs.om.impl.PropertyKeyImpl@ec8784]],
> > [nodeProperties, []], [creationDate, 2004-03-01
> > 09:34:13.138], [modifiedDate, 2004-03-01
> > 10:03:14.802]]
> >
> >
> > Regards,
> >
> > David.
> >
> > --- Oleg Nitz <on...@ukr.net> wrote:
> > > On Sunday 29 February 2004 19:24, David Le Strat
> > >
> > > wrote:
> > > > When I update the NodeImpl with new
> nodeProperties
> > >
> > > (a
> > >
> > > > collection), only the NodeImpl object gets
> updated
> > >
> > > and
> > >
> > > > the nodeProperies are not created.
> > > >
> > > > I have done this in the past with PB with out
> any
> > > > issues.  Any suggestions?
> > >
> > > With auto-update="true" nodeProperties should be
> > > creates, whatever you use,
> > > PB or OTM. I've just done correspondent test
> with
> > > OTM, and all is okay.
> > > So please send me code snippet or just try to do
> the
> > > same with PB.
> > > OTM does nothing special when
> auto-update="true", it
> > > just calls
> > > broker.store(). If you set auto-update="false"
> and
> > > otm-dependent="true", then
> > > OTM itself will take care about creation and
> > > deletion of nodeProperties.
> > >
> > > Regards,
> > >  Oleg
> >
> >
>
---------------------------------------------------------------------
> >
> > > To unsubscribe, e-mail:
> > > ojb-user-unsubscribe@db.apache.org
> > > For additional commands, e-mail:
> > > ojb-user-help@db.apache.org
> >
> > __________________________________
> > Do you Yahoo!?
> > Get better spam protection with Yahoo! Mail.
> > http://antispam.yahoo.com/tools
> >
> >
>
---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> ojb-user-unsubscribe@db.apache.org
> > For additional commands, e-mail:
> ojb-user-help@db.apache.org
> 
> 
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> ojb-user-unsubscribe@db.apache.org
> For additional commands, e-mail:
> ojb-user-help@db.apache.org
> 


__________________________________
Do you Yahoo!?
Yahoo! Search - Find what you�re looking for faster
http://search.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-user-help@db.apache.org

Re: [OTM] collection-descriptor issue with latest from head.

Posted by Oleg Nitz <on...@ukr.net>.
Hi David,

Can you give at least a small code snippet, please?

Regards,
 Oleg

On Monday 01 March 2004 15:12, David Le Strat wrote:
> Hello,
>
> I am having the weirdest issue, any suggestion;
>
> Basically, I want to add a collection of properties to
> a node.
>
> In my test, I have only 1 property:
>
> Properties: [[nodeId, 5], [propertyKeyId, 21],
> [propertyKey,
> org.apache.jetspeed.prefs.om.impl.PropertyKeyImpl@162d950],
> [propertyValue, true], [creationDate, 2004-03-01
> 10:03:14.812], [modifiedDate, 2004-03-01
> 10:03:14.812]]
>
> I open the transaction and do setNodeProperties on the
> node object.
>
> The transaction is open, just before committing, I
> check to see that the properties are set correctly on
> the object:
>
> DEBUG: org.apache.jetspeed.prefs.impl.PreferencesImpl
> -
>
> Node for update: [[parentNodeId, 4], [nodeName,
> propertyset1], [fullPath,
> /user/principal1/propertyset1], [nodeType, 0],
> [nodeKeys,
> [org.apache.jetspeed.prefs.om.impl.PropertyKeyImpl@952905,
> org.apache.jetspeed.prefs.om.impl.PropertyKeyImpl@b83be0,
> org.apache.jetspeed.prefs.om.impl.PropertyKeyImpl@1
> 631573,
> org.apache.jetspeed.prefs.om.impl.PropertyKeyImpl@1533c8]],
> [nodeProperties, [[[nodeId, 5], [propertyKeyId, 21],
> [propertyKey,
> org.apache.jetspeed.prefs.om.impl.PropertyKeyImpl@162d950],
> [propertyValue, true], [creationDate, 2004-03-01
> 10:03:14.812], [modifiedDate, 2004-03-01
> 10:03:14.812]]]
> ], [creationDate, 2004-03-01 09:34:13.138],
> [modifiedDate, 2004-03-01 10:03:14.812]]
>
>
> As you can see [nodeProperties,...] is set, I also
> change the [modifiedDate, ...].
>
> When I close the transaction, I get [nodeProperties,
> []]: the nodeProperties collection is gone...
>
> But [modifiedDate, 2004-03-01 10:03:14.802] is still
> there.
>
> I can't think of anything that would cause this
> behavior.  Any help is appreciated.
>
>
> DEBUG:
> org.apache.ojb.broker.accesslayer.JdbcAccessImpl -
> executeUpdate : [[parentNodeId, 4], [nodeName,
> propertyset1], [fullPath,
> /user/principal1/propertyset1], [nodeType, 0],
> [nodeKeys,
> [org.apache.jetspeed.prefs.om.impl.PropertyKeyImpl@162d950,
> org.apache.jetspeed.prefs.om.impl.PropertyKeyImpl@a
> 937cd,
> org.apache.jetspeed.prefs.om.impl.PropertyKeyImpl@18e899c,
> org.apache.jetspeed.prefs.om.impl.PropertyKeyImpl@ec8784]],
> [nodeProperties, []], [creationDate, 2004-03-01
> 09:34:13.138], [modifiedDate, 2004-03-01
> 10:03:14.802]]
> DEBUG:
> org.apache.ojb.broker.accesslayer.JdbcAccessImpl -
> executeUpdate : [[parentNodeId, 4], [nodeName,
> propertyset1], [fullPath,
> /user/principal1/propertyset1], [nodeType, 0],
> [nodeKeys,
> [org.apache.jetspeed.prefs.om.impl.PropertyKeyImpl@162d950,
> org.apache.jetspeed.prefs.om.impl.PropertyKeyImpl@a
> 937cd,
> org.apache.jetspeed.prefs.om.impl.PropertyKeyImpl@18e899c,
> org.apache.jetspeed.prefs.om.impl.PropertyKeyImpl@ec8784]],
> [nodeProperties, []], [creationDate, 2004-03-01
> 09:34:13.138], [modifiedDate, 2004-03-01
> 10:03:14.802]]
>
>
> Regards,
>
> David.
>
> --- Oleg Nitz <on...@ukr.net> wrote:
> > On Sunday 29 February 2004 19:24, David Le Strat
> >
> > wrote:
> > > When I update the NodeImpl with new nodeProperties
> >
> > (a
> >
> > > collection), only the NodeImpl object gets updated
> >
> > and
> >
> > > the nodeProperies are not created.
> > >
> > > I have done this in the past with PB with out any
> > > issues.  Any suggestions?
> >
> > With auto-update="true" nodeProperties should be
> > creates, whatever you use,
> > PB or OTM. I've just done correspondent test with
> > OTM, and all is okay.
> > So please send me code snippet or just try to do the
> > same with PB.
> > OTM does nothing special when auto-update="true", it
> > just calls
> > broker.store(). If you set auto-update="false" and
> > otm-dependent="true", then
> > OTM itself will take care about creation and
> > deletion of nodeProperties.
> >
> > Regards,
> >  Oleg
>
> ---------------------------------------------------------------------
>
> > To unsubscribe, e-mail:
> > ojb-user-unsubscribe@db.apache.org
> > For additional commands, e-mail:
> > ojb-user-help@db.apache.org
>
> __________________________________
> Do you Yahoo!?
> Get better spam protection with Yahoo! Mail.
> http://antispam.yahoo.com/tools
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-user-help@db.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-user-help@db.apache.org

Re: [OTM] collection-descriptor issue with latest from head.

Posted by David Le Strat <dl...@yahoo.com>.
Hello,

I am having the weirdest issue, any suggestion;

Basically, I want to add a collection of properties to
a node.

In my test, I have only 1 property:

Properties: [[nodeId, 5], [propertyKeyId, 21],
[propertyKey,
org.apache.jetspeed.prefs.om.impl.PropertyKeyImpl@162d950],
[propertyValue, true], [creationDate, 2004-03-01
10:03:14.812], [modifiedDate, 2004-03-01
10:03:14.812]]

I open the transaction and do setNodeProperties on the
node object.

The transaction is open, just before committing, I
check to see that the properties are set correctly on
the object:

DEBUG: org.apache.jetspeed.prefs.impl.PreferencesImpl
-

Node for update: [[parentNodeId, 4], [nodeName,
propertyset1], [fullPath,
/user/principal1/propertyset1], [nodeType, 0],
[nodeKeys,
[org.apache.jetspeed.prefs.om.impl.PropertyKeyImpl@952905,
org.apache.jetspeed.prefs.om.impl.PropertyKeyImpl@b83be0,
org.apache.jetspeed.prefs.om.impl.PropertyKeyImpl@1
631573,
org.apache.jetspeed.prefs.om.impl.PropertyKeyImpl@1533c8]],
[nodeProperties, [[[nodeId, 5], [propertyKeyId, 21],
[propertyKey,
org.apache.jetspeed.prefs.om.impl.PropertyKeyImpl@162d950],
[propertyValue, true], [creationDate, 2004-03-01
10:03:14.812], [modifiedDate, 2004-03-01
10:03:14.812]]]
], [creationDate, 2004-03-01 09:34:13.138],
[modifiedDate, 2004-03-01 10:03:14.812]]


As you can see [nodeProperties,...] is set, I also
change the [modifiedDate, ...].

When I close the transaction, I get [nodeProperties,
[]]: the nodeProperties collection is gone...

But [modifiedDate, 2004-03-01 10:03:14.802] is still
there.

I can't think of anything that would cause this
behavior.  Any help is appreciated.


DEBUG:
org.apache.ojb.broker.accesslayer.JdbcAccessImpl -
executeUpdate : [[parentNodeId, 4], [nodeName,
propertyset1], [fullPath,
/user/principal1/propertyset1], [nodeType, 0],
[nodeKeys,
[org.apache.jetspeed.prefs.om.impl.PropertyKeyImpl@162d950,
org.apache.jetspeed.prefs.om.impl.PropertyKeyImpl@a
937cd,
org.apache.jetspeed.prefs.om.impl.PropertyKeyImpl@18e899c,
org.apache.jetspeed.prefs.om.impl.PropertyKeyImpl@ec8784]],
[nodeProperties, []], [creationDate, 2004-03-01
09:34:13.138], [modifiedDate, 2004-03-01
10:03:14.802]]
DEBUG:
org.apache.ojb.broker.accesslayer.JdbcAccessImpl -
executeUpdate : [[parentNodeId, 4], [nodeName,
propertyset1], [fullPath,
/user/principal1/propertyset1], [nodeType, 0],
[nodeKeys,
[org.apache.jetspeed.prefs.om.impl.PropertyKeyImpl@162d950,
org.apache.jetspeed.prefs.om.impl.PropertyKeyImpl@a
937cd,
org.apache.jetspeed.prefs.om.impl.PropertyKeyImpl@18e899c,
org.apache.jetspeed.prefs.om.impl.PropertyKeyImpl@ec8784]],
[nodeProperties, []], [creationDate, 2004-03-01
09:34:13.138], [modifiedDate, 2004-03-01
10:03:14.802]]


Regards,

David.


--- Oleg Nitz <on...@ukr.net> wrote:
> On Sunday 29 February 2004 19:24, David Le Strat
> wrote:
> > When I update the NodeImpl with new nodeProperties
> (a
> > collection), only the NodeImpl object gets updated
> and
> > the nodeProperies are not created.
> >
> > I have done this in the past with PB with out any
> > issues.  Any suggestions?
> With auto-update="true" nodeProperties should be
> creates, whatever you use, 
> PB or OTM. I've just done correspondent test with
> OTM, and all is okay.
> So please send me code snippet or just try to do the
> same with PB.
> OTM does nothing special when auto-update="true", it
> just calls 
> broker.store(). If you set auto-update="false" and
> otm-dependent="true", then 
> OTM itself will take care about creation and
> deletion of nodeProperties.
> 
> Regards,
>  Oleg
> 
> 
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> ojb-user-unsubscribe@db.apache.org
> For additional commands, e-mail:
> ojb-user-help@db.apache.org
> 


__________________________________
Do you Yahoo!?
Get better spam protection with Yahoo! Mail.
http://antispam.yahoo.com/tools

---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-user-help@db.apache.org

Re: [OTM] collection-descriptor issue with latest from head.

Posted by Oleg Nitz <on...@ukr.net>.
On Sunday 29 February 2004 19:24, David Le Strat wrote:
> When I update the NodeImpl with new nodeProperties (a
> collection), only the NodeImpl object gets updated and
> the nodeProperies are not created.
>
> I have done this in the past with PB with out any
> issues.  Any suggestions?
With auto-update="true" nodeProperties should be creates, whatever you use, 
PB or OTM. I've just done correspondent test with OTM, and all is okay.
So please send me code snippet or just try to do the same with PB.
OTM does nothing special when auto-update="true", it just calls 
broker.store(). If you set auto-update="false" and otm-dependent="true", then 
OTM itself will take care about creation and deletion of nodeProperties.

Regards,
 Oleg


---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-user-help@db.apache.org

[OTM] collection-descriptor issue with latest from head. [WAS] Collection Re: OTM M-N Mapping Issue

Posted by David Le Strat <dl...@yahoo.com>.
Hi there,

Oleg fix solved my problem with foreign key violation.
 I am now having another issue with OTM.

I have:
<class-descriptor
    class="org.apache.jetspeed.prefs.om.impl.NodeImpl"
    table="PREFS_NODE"
>
....
<collection-descriptor
        name="nodeProperties"
       
element-class-ref="org.apache.jetspeed.prefs.om.impl.PropertyImpl"
        refresh="true"
        auto-delete="false"
      	auto-update = "true"
      	auto-retrieve = "true"
    >
        <documentation>This is the reference to a node
properties.</documentation>
        <inverse-foreignkey field-ref="nodeId"/>
    </collection-descriptor>
....

When I update the NodeImpl with new nodeProperties (a
collection), only the NodeImpl object gets updated and
the nodeProperies are not created.

I have done this in the past with PB with out any
issues.  Any suggestions?

Thanks.

David Le Strat.
_______________________________

Debug Log:

DEBUG: org.apache.ojb.broker.accesslayer.RsIterator -
RsIterator[org.apache.ojb.broker.accesslayer.RsQueryObject[query:
Query from class
org.apache.jetspeed.prefs.om.impl.PropertyImpl where
[nodeId = 5], class descriptor:
org.apache.jetspeed.prefs.om.impl.PropertyImpl]]
initialized
DEBUG: org.apache.ojb.broker.accesslayer.RsIterator -
hasNext() -> false
DEBUG: org.apache.ojb.broker.accesslayer.RsIterator -
hasNext() -> false
DEBUG: org.apache.jetspeed.prefs.impl.PreferencesImpl
- New property value: [propertyName0, true]
DEBUG: org.apache.jetspeed.prefs.impl.PreferencesImpl
- Updated properties: 1
DEBUG:
org.apache.ojb.broker.accesslayer.JdbcAccessImpl -
executeUpdate : [[parentNodeId, 4], [nodeName,
propertyset1], [nodeType, 0], [fullPath,
/user/principal1/propertyset1], [creationDate,
2004-02-29 02:40:29.378], [modifiedDate, 2004-02-29
14:04:45.144]]
DEBUG:
org.apache.ojb.broker.accesslayer.JdbcAccessImpl -
executeUpdate : [[parentNodeId, 4], [nodeName,
propertyset1], [nodeType, 0], [fullPath,
/user/principal1/propertyset1], [creationDate,
2004-02-29 02:40:29.378], [modifiedDate, 2004-02-29
14:04:45.144]]
DEBUG:
org.apache.ojb.broker.accesslayer.sql.SqlGeneratorDefaultImpl
- SQL:UPDATE PREFS_NODE SET
PARENT_NODE_ID=?,NODE_NAME=?,NODE_TYPE=?,FULL_PATH=?,CREATION_DATE=?,MODIFIED_DATE=?
WHERE NODE_ID = ?
DEBUG:
org.apache.ojb.broker.accesslayer.sql.SqlGeneratorDefaultImpl
- SQL:UPDATE PREFS_NODE SET
PARENT_NODE_ID=?,NODE_NAME=?,NODE_TYPE=?,FULL_PATH=?,CREATION_DATE=?,MODIFIED_DATE=?
WHERE NODE_ID = ?
DEBUG:
org.apache.ojb.broker.accesslayer.JdbcAccessImpl -
executeUpdate:
org.apache.commons.dbcp.DelegatingPreparedStatement@145fe3b
DEBUG:
org.apache.ojb.broker.accesslayer.JdbcAccessImpl -
executeUpdate:
org.apache.commons.dbcp.DelegatingPreparedStatement@145fe3b
DEBUG:
org.apache.ojb.broker.accesslayer.StatementManager -
closeResources was called
DEBUG:
org.apache.ojb.broker.accesslayer.StatementManager -
closeResources was called

--- Oleg Nitz <on...@ukr.net> wrote:
> Hi David,
> 
> If you use otm-dependent relations, then check the
> current CVS HEAD - I've 
> just committed the fix. If not, then give more
> detailed description of your 
> case.
> 
> Regards,
>  Oleg
> 
> On Sunday 29 February 2004 08:09, David Le Strat
> wrote:
> > Hello there,
> >
> > I am using OTM with M-N mapping. I am having an
> issue
> > with OTM, where OJB violate foreign key
> constraints.
> >
> > I have the following mapping:
> >
> > PREFS_NODE <-- PREFS_NODE_PROPERTY_KEY -->
> > PREFS_PROPERTY_KEY
> >
> > With OTM, OJB tries to delete PREFS_PROPERTY_KEY
> > before removing PREFS_NODE_PROPERTY_KEY therefore
> > violating foreign key constraint.  Has anybody
> else
> > experienced the same behavior.
> >
> > Regards,
> >
> > David Le Strat.
> >
> > __________________________________
> > Do you Yahoo!?
> > Get better spam protection with Yahoo! Mail.
> > http://antispam.yahoo.com/tools
> >
> >
>
---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> ojb-user-unsubscribe@db.apache.org
> > For additional commands, e-mail:
> ojb-user-help@db.apache.org
> 
> 
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> ojb-user-unsubscribe@db.apache.org
> For additional commands, e-mail:
> ojb-user-help@db.apache.org
> 


__________________________________
Do you Yahoo!?
Get better spam protection with Yahoo! Mail.
http://antispam.yahoo.com/tools

---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-user-help@db.apache.org

Re: OTM M-N Mapping Issue

Posted by David Le Strat <dl...@yahoo.com>.
Thanks Oleg, just saw your commit ;).  I use OTM. I
will try the latest head.

Regards,

David.
--- Oleg Nitz <on...@ukr.net> wrote:
> Hi David,
> 
> If you use otm-dependent relations, then check the
> current CVS HEAD - I've 
> just committed the fix. If not, then give more
> detailed description of your 
> case.
> 
> Regards,
>  Oleg
> 
> On Sunday 29 February 2004 08:09, David Le Strat
> wrote:
> > Hello there,
> >
> > I am using OTM with M-N mapping. I am having an
> issue
> > with OTM, where OJB violate foreign key
> constraints.
> >
> > I have the following mapping:
> >
> > PREFS_NODE <-- PREFS_NODE_PROPERTY_KEY -->
> > PREFS_PROPERTY_KEY
> >
> > With OTM, OJB tries to delete PREFS_PROPERTY_KEY
> > before removing PREFS_NODE_PROPERTY_KEY therefore
> > violating foreign key constraint.  Has anybody
> else
> > experienced the same behavior.
> >
> > Regards,
> >
> > David Le Strat.
> >
> > __________________________________
> > Do you Yahoo!?
> > Get better spam protection with Yahoo! Mail.
> > http://antispam.yahoo.com/tools
> >
> >
>
---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> ojb-user-unsubscribe@db.apache.org
> > For additional commands, e-mail:
> ojb-user-help@db.apache.org
> 
> 
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> ojb-user-unsubscribe@db.apache.org
> For additional commands, e-mail:
> ojb-user-help@db.apache.org
> 


__________________________________
Do you Yahoo!?
Get better spam protection with Yahoo! Mail.
http://antispam.yahoo.com/tools

---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-user-help@db.apache.org

Re: OTM M-N Mapping Issue

Posted by Oleg Nitz <on...@ukr.net>.
Hi David,

If you use otm-dependent relations, then check the current CVS HEAD - I've 
just committed the fix. If not, then give more detailed description of your 
case.

Regards,
 Oleg

On Sunday 29 February 2004 08:09, David Le Strat wrote:
> Hello there,
>
> I am using OTM with M-N mapping. I am having an issue
> with OTM, where OJB violate foreign key constraints.
>
> I have the following mapping:
>
> PREFS_NODE <-- PREFS_NODE_PROPERTY_KEY -->
> PREFS_PROPERTY_KEY
>
> With OTM, OJB tries to delete PREFS_PROPERTY_KEY
> before removing PREFS_NODE_PROPERTY_KEY therefore
> violating foreign key constraint.  Has anybody else
> experienced the same behavior.
>
> Regards,
>
> David Le Strat.
>
> __________________________________
> Do you Yahoo!?
> Get better spam protection with Yahoo! Mail.
> http://antispam.yahoo.com/tools
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-user-help@db.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-user-help@db.apache.org