Hi folks!

I have migrated from LLBLGen v2.0 to v3.0. Everything runs fine, except that fields position have changed in some table.

It seems that fields are now sorted alphabetically, at least for primary keys. It's an issue for me, as every entity instantiation in my code have to be reviewed, to change argument order in constructor.

For exemple, this instantiation is no longer correct :

PARAMETRE_TOP1Entity top1 = new PARAMETRE_TOP1Entity(dateDebut, dateFin, codeRegroupement, sProfilGRD, typeEngagement, typePrix);

With LLBLGen v3, it has to be :

PARAMETRE_TOP1Entity top1 = new PARAMETRE_TOP1Entity(dateDebut, dateFin, sProfilGRD, codeRegroupement, typeEngagement, typePrix);

Do you have a solution to maintain old position order?

Thank you!

Kal

It looks like a breaking change of LLBLGen v3, according to the ChangeLog. I'm gonna check all my code then

Cheers, Kal

Correct, this is an unfortunate breaking change for V3. It has been discussed at some length on the forum, and it is pretty much guaranteed that we will not be reverting to the 2.6 system.

So yep, checking all of your code is the way to go.

Matt

In v3.1, we'll add a feature which allows you to order the fields to your liking. This isn't completely as v2.6, as with multiple db targets, keeping things in sync with both db's could be impossible (e.g. when the target tables have different ordering of the fields).

If you want to know for which entities this problem pops up, you can use element search in the designer and use this code: http://www.llblgen.com/tinyforum/GotoMessage.aspx?MessageID=104475&ThreadID=18633

Otis wrote:

In v3.1, we'll add a feature which allows you to order the fields to your liking. This isn't completely as v2.6, as with multiple db targets, keeping things in sync with both db's could be impossible (e.g. when the target tables have different ordering of the fields).

If you want to know for which entities this problem pops up, you can use element search in the designer and use this code: http://www.llblgen.com/tinyforum/GotoMessage.aspx?MessageID=104475&ThreadID=18633

That's a nice feature!

Thanks for your answer! Cheers