Composite Primary Key about npoco

[schotime]

At the moment you can't. Can you elaborate on the scenario you are trying to enable?

[enriko-riba]

As always with such stuff: new project, foreign DB which I am not supposed to change...
Table has a composite PK where one of them is Identity and the other is is not. Currently its all or nothing regarding the autoincrement - which is fine, until you stumble upon a table like this.
I solved this particular problem with good old SQL Execute but it kinda defeats the purpose...

[schotime]

Ok...I think I understand the issue. I'll have to look into what can be done, because at the moment autoIncrement is just true or false.

[enriko-riba]

Would it make sense to add autoincrement on the field level instead of the class level? It would behave just like the ResultColumn attribute.

[schotime]

It might, however I need to look at the implications of that...not just for Sql Server as well.

[rganz]

Oh... for me this is a serious issue. I have distributed tables over various locations, and they are merged in a central location, so that an autoincrement is not enough. I need at least an additional location field in the primary key...

[rganz]

Sorry, I was too fast... As I see, a composite Primary Key is possible, just not with an autoincrement. Unfortunately in another table I need exactly this as well...