In v3.0, is it possible to include the field name in the generated PK name?

For example we have a table named Order with OrderId as the pk. Currently the generated PK name would look like this:

PK_30000c543c9b400d3ba17c247e7

I would like it to look like this:

PK_OrderId_30000c543c9b400d3ba17c247e7

Can that be done?

Thanks

No, not at the moment.

In general these constraints have unique names (with a guid) as they need to be unique inside a catalog / schema. This means that if they're not unique among a catalog/schema, you'll get errors when you apply the script. To avoid having name clashes and also names which are too long (for some databases), we use the guid approach.

We have logged some change requests for a pattern system similar to the name patterns for model element names, we'll look into that in a future v3.x version.

(see this discussion: http://www.llblgen.com/tinyforum/Messages.aspx?ThreadID=18206)