This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
We are using IdentityColumn for our Identity method. (Yes, we've read the LS documentation about its performance disadvantages, but we've decided to stick with the devil we know ;-) It's all working fine except for one thing: when we use "automatic" "through" associations, the entity generated by LightSpeed does not use the IdentityColumn identity method. Perhaps one possible solution would be for IdentityMethod to be specifiable under Policies -> Defaults Policy, and for the auto-generated entities to respect those defaults.... But, is there any solution available now in LS 4? Thanks, John |
|
|
Hi John, No there isn't anyway to control this currently - you will need to fix this up in the database. I am presuming this is only an issue for schema generation as you can control the default identity method on the context?
|
|
|
Yes, your assumption is correct. As you might be able to tell from some of my questions in other threads, we are trying to use a model (Designer)-driven approach. Ideally for us, this would involve no hand editing of schema creation scripts. We are liking the quick turn-around that this approach gives us, but there are some "gotchas" - such as the issue we're discussing in this thread. We'd certainly like it if LS 5 could remove some of the pain points in the totally model-driven approach. :-) FYI our solution to the particular issue in this thread is simply to use explicit "through" entities instead of automatic ones. |
|