Hi,

I'm just starting out evaluating LLBLGen Pro and have a question that I haven't found an answer to here.

Using LLBLGen Pro, 2.6 Final against an existing Oracle database using ODP.Net.

I'm trying to set up a custom relation. On the LISTING table, I have a CUSTOMER_ID that is a fk to CUSTOMER table. But on the CUSTOMER table, the pk is CUSTOMER_ID and VERSION.

However, VERSION is always = 1, so I'd like to be able to set up a relation solely on CUSTOMER_ID, or else on both columns but set VERSION = 1, not a column in LISTING.

LLBLGen Pro wants a matching column for the VERSION field, which I don't have, so it won't create the relation for me.

Has anyone done similar? Is this possible in some way, even through custom code? Our db is full of this type of pk/fk issue so this is a make or break issue for us.

(Yes, I know, it's a screwy setup. It's a legacy system and we can't change pk/fk columns because of existing closed applications running against the db, sorry. I don't like it either.)

Thanks for any pointers, Jason

Hi Jason -

Ahh, yes - I see some Table History going on. Yes, of course this is possible with LLBLGen Pro.

Are you going to be using Adapter of Self-Servicing?

I am positive there are many ways to attack this beast. Here's what I would do - You're going to want to look at the RelationClasses that are generated. For instance, You'll notice the code below is found within any file in the RelationClasses folder that is generated for you:

        Public Overridable  ReadOnly Property QuickbooksItemEntityUsingId() As IEntityRelation
            Get
                Dim relation As IEntityRelation = New EntityRelation(SD.LLBLGen.Pro.ORMSupportClasses.RelationType.OneToOne, "QuickbooksItem", False)

                relation.AddEntityFieldPair(QuickbooksItemFields.ListId, ItemDetailFields.Id)

                relation.InheritanceInfoPkSideEntity = InheritanceInfoProviderSingleton.GetInstance().GetInheritanceInfo("QuickbooksItemEntity", False)
                relation.InheritanceInfoFkSideEntity = InheritanceInfoProviderSingleton.GetInstance().GetInheritanceInfo("ItemDetailEntity", True)
                Return relation
            End Get
        End Property

I would use the relation.CustomFilter to append VersionField=1 to the Table Join. Start out with editing the generated Relations code (shown above) and make sure it does what you want. Then, can edit the Templates so this code will be generated for you on all tables.

Good luck! Hope this helps!

Ryan

Well if the VERSION field has no use, since it's always 1 and you don't use it in relation. Then maybe it's better that you copy the db schema, drop this field from the table, generate the LLBLGen Pro project against this copy schema, then use the genarted code to target the Original schema.

This way LLBLGen Pro will know nothing about the Version field and anything else you choose to clean up from the old schema.

Good point, I don't know why I didn't think of that. Thanks for both suggestions guys.