ATG 2007.1 Versioned Repositories

[David Stableforth ()]

Hello,

I have a repository with a one-to-many relationship, A - B, where A is the primary table and B is a "multi" table shared inside of A repository item.  B however is declared as primary in its own item descriptor and it works fine on my original module.

However, when I started my versioned module with PubPortlet myModule I get errors saying:

 [MyContentRepository_ver] Found a one-to-many shared table definition in versioned case with one side using a primary table. These types of relationships are not supported by VersionRepository.


Apparently in 2007.1 the "non" multi table must declared auxiliary, it can't be primary.  But, if I changed the primary tables to auxiliary, then none of my versioned tables (for myRepository) would be primary tables and I'm wondering how would the versioning work if there weren't any primary tables on myRepository

I don't remember this constraint in previous versions, has anyone else experienced this in 2007.1?

thanks for reading,


***********UPDATE*********  

Instead of implementing a shared table, I switched to using a mapping table instead, EG. inside of my
repository definition for item A i have a mapping table with two id's my primary from A and my primary from B.  This way both tables can be primary, which is essential for CA to work, with the 8 additional columns that one adds to each primary table of a versioned repository.  A simple enough solution, but ATG documentation tells me to do it their way, you know the drill...

BTW, I haven't had any responses on Nabble,  although I  hear http://groups.google.com/group/atg_tech
is pretty good.

thanks again.