Thanks - just trying to help you guys out in case anyone else tries the link. Cheers
You're welcome - more than happy to help. If it is a bug could the ticket get refunded? - Thanks, John
Yes, around 12. Only happened after update from 5.3.1 to 5.3.2
i have created feature request - please delete this and refund question. thank you.
Correct, for the scenario outlined yes.
please if you could refund my ticket count that would be great...
CRUD Generation - allow the option to select one or more Properties to become part of a Unique Constraint.
This is a very common requirement across the projects I've worked on and although it can be enforced in other layers - I think having these constraints at the DB layer is best practice for a strong system.
Example: EF SQL Server multi-tenant app - generated code might look something like:
ABP Suite - Preserve Custom Code Across Repeated CRUD Generations
my common work-flow: generate crud->customise->re-generate crud->re-enter-previous customization-> repeat...etc
`#region CustomCode
// ...custom code here
#endregion`
This would be a massive boost in efficiency and a valued Feature in my opinion.
GUID properties type
SQL Server has `uniqueidentifier' - or did you mean something else?