Default IdentityMethod based on Guid when running lsgen.exe (designer)

If I running lsgen.exe now the "IdentyMethod" is empty. It could be nice in model-level to say that every table with Guid as identity use "IdentityMethod.Guid"

Then I don't need to a manually update after running lsgen.exe

(This post is the same as in http://www.mindscape.co.nz/forums/Thread.aspx?ThreadID=1587, but trying to explain it better)

I have logged a feature request for this but it is a little bit more complicated than you might like.  Since you don't need to specify table-level identity methods in a homogeneous database (e.g. where all PKs are GUIDs),  what you are effectively asking for is for us to auto-infer identity methods in mixed databases (where some PKs are numeric and some are GUIDs).  This raises a couple of issues:

1. We don't know whether int or GUID is the "baseline" PK type (specified on the LightSpeedContext) and which is the "exception" (specified via TableAttribute).  Of course one way around this is to emit table-level identity methods for all tables.

2. For int PKs, we don't know whether to emit KeyTable, Sequence or IdentityColumn.  For GUID PKs, we don't know whether to emit Guid, GuidComb or IdentityColumn.  Obviously we can ask the user to specify but this does add some complexity to the command-line interface and to the implementation.  We will have a think about this and see how we go. 

 Could the config feature be a solution there you can define in the "config contract" either model-level or table-level different options/features...

http://www.mindscape.co.nz/forums/Thread.aspx?ThreadID=1604

 Perhaps also you could group a set of tables at link a feature-set to the group...