Thank you for the reply.
Yes, I do agree it is not a big issue. But it is helpful when documenting and collaborating with the client and teammates. For example, when you try explaining the model to your fellow teammates or clients (tech savvy ones), it would help if we have
the columns in the order of creation (or rather in the order we want it to be placed) so that related columns come one after another.
For example, lets take a sample table called "ENTITY" which I created, the columns in that table would be:
entity_address and so on...
If you look at the above explanation I display "entity_id" at the start of the list for the reason it is the primary key and thats where the discussion about this model starts off. Then logically speaking we proceed with the name, email id, address,
telephone number and so on
But when we add this model to nHydrate it puts the column as
entity_id ... and so on
It would be hard to do a cross check of a paper / notepad written model towards a nHydrate model because the columns are not in the order that we would like them to be.
As I agreed, this is not critical as in a functional sort of way, but when it comes down to collaboration it makes sense.