LLBLGen.com Forums General feed

typed IPredicate by zivtir

zivtir — Tue, 07 Sep 2010 10:53:12 GMT

Hi
i m using this code:

internal void RunUpdatePredicateExpression(EntityBase2 entityToUpdate, IPredicate[] predicates)
        {
            IRelationPredicateBucket filter = new RelationPredicateBucket();
            foreach (var item in predicates)
            {
                filter.PredicateExpression.AddWithAnd(item);
            }
            using (IDataAccessAdapter adapter = this.DataAccessAdapterProvider.GetAdapter())
            {
                adapter.UpdateEntitiesDirectly(entityToUpdate, filter);
            }
        }
now i want that the IPredicate be for specific entity on the declaration of the function.
it prevent runtime error when i try to add Predicates which are not match the entityToUpdate.
how can i manage it?
thanks

Getting Graph by Walaa

Walaa — Mon, 06 Sep 2010 13:26:49 GMT

You should avoid loading the full graph as much as possible.
This can lead to loading the entire database into memory.

Getting Graph by alexvdb25

alexvdb25 — Mon, 06 Sep 2010 11:04:24 GMT

Hi,

Is there a way to automatically load the full graph for a particular entity by code?

I want to write a generic function which determines at run-time which related entities should be loaded....

Is this possible?

Thanks and best regards,
Alex

Foreign key must be defined in database for v3.0? by Otis

Otis — Sat, 04 Sep 2010 09:42:13 GMT

We are aware of this situation, and we will address this in 3.1. The main problem is that the relationship in the model always has to have an equivalent FK in the relational model, or if you set a setting it simply won't need that, but that's a black/white switch, there's a grey area where you for SOME relationships you want this behavior and for some others you don't.

In general people won't run into this that often, but edge cases can happen which might force you to jump though hoops. My question to you is: if you can't add the FK to the DB, due to bad data, don't you think it will bug you at runtime when you fetch that data and it will turn out that the data is inconsistent and thus for example Fk field values don't match any PK value?

Identity columns SQL Server and updating Entities by Otis

Otis — Fri, 03 Sep 2010 15:55:31 GMT

PaulWilson wrote:

Thanks - have found it. Few questions:

a) It is possible to set a default to @@IDENTITY

No. @@IDENTITY is in general discouraged. It is only necessary when triggers are used which affect the scope's identity value.

Quote:

b) Is it possible to bulk update all entities to use @@IDENTITY

Yes, two ways:
1) open the llblgenproj file in notepad, then global replace
SequenceToUse="SCOPE_IDENTITY()"
with
SequenceToUse="@@IDENTITY"

or
2) with Element search, using a query over the mappings, then update the field mappings with a different DBSequence object, however it's a tad complex to do this (but doable). So it's easier to use option 1).

If you want option 2) (e.g. you want only a subset of the number of entities being updated to @@IDENTITY, let us know so we can formulate the piece of code for you to run in element search.

Foreign key must be defined in database for v3.0? by carni4

carni4 — Fri, 03 Sep 2010 15:44:19 GMT

Is there by chance a way to turn off the requirement that relationships defined in the designer be set to foreign keys in the database, without turning off the creation of new relationships based on discovered foreign key constraints?

Basically what I have is some bad/old data that prevents the creation of a few foreign key constraints (and I don't have time to investigate the possibility of nulling that bad data out at the moment), but I need the LLBLGen relationships to be there. The RelationshipsFollowDBForeignKeyConstraints setting mentioned in this thread helps me with that situation obviously, but won't it prevent database refreshes from recognizing new relationships that exist in the database but not in LLBLGen? What happens if I create a series of new tables and refresh the database? Will the relationships based on FKs in the new tables not be created in LLBLGen? I am pained when I think of having to remember to manually create the relationships every time.

Thank you in advance for your attention.

Identity columns SQL Server and updating Entities by PaulWilson

PaulWilson — Fri, 03 Sep 2010 11:40:27 GMT

Thanks - have found it. Few questions:

a) It is possible to set a default to @@IDENTITY
b) Is it possible to bulk update all entities to use @@IDENTITY

ORMValueTypeMismatchException was unhandled by user code by PaulWilson

PaulWilson — Fri, 03 Sep 2010 11:37:10 GMT

This is related to using triggers with SCOPE_IDENTITY and is solved by updating the Field Mapping of the Entity and altering 'sequence' to @@IDENTITY (assuming that the trigger doesn't change this value).

Please see http://www.llblgen.com/tinyforum/Messages.aspx?ThreadID=18605

Identity columns SQL Server and updating Entities by Otis

Otis — Fri, 03 Sep 2010 11:25:01 GMT

PaulWilson wrote:

I started replying about 2 hours ago, then got called into meetings so I didn't see your reply Otis. I can't find where I'd switch sequence mapping. There is a sequence in the preferences SEQ_{$EntityName} butI can't find it anywhere else. Where should I be looking.

Open the entity in the entity editor, go to 'field mappings' tab, you'll see the SCOPE_IDENTITY() sequence right next to the field which is the PK. Change it to @@IDENTITY.

SCOPE_IDENTITY doesn't work with triggers AND identity inserts, because the scope of the trigger is different.

Identity columns SQL Server and updating Entities by PaulWilson

PaulWilson — Fri, 03 Sep 2010 10:29:50 GMT