Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Hi Rob, I have implemented a support for key on multiple column. Give me #50

Closed
wants to merge 5 commits into
from

Conversation

Projects
None yet
2 participants

Hi Rob, I have implemented a support for key on multiple column. Give me your feed back.

apacifico added some commits Jun 1, 2011

Introduce delete support in the BuildCommands method. The object need…
…s to provide a property 'Remove' with boolean type and a Primary key to be detected as an objected to be deleted in database.
Introduce ambient transaction for the execute method. The method dete…
…ct if an ambient transaction exists or create a connexion transaction. With the ambiant transaction we can save diffent object in one transaction. Require a reference to System.Transaction assembly.
Contributor

robconery commented Jun 19, 2011

There are a lot of changes here. I've had this discussion with others (using SubSonic) with respect to composite keys and to be honest - that's more code than I'd like to use to support what I consider an edge case (and not a terribly good database design outside of many to many joins)

@robconery robconery closed this Jun 19, 2011

Hi Rob,
I'm agree with your response but what to do with an existing database. I
have the case today for a customer in insurance having an existing database
but needs new features. He want not to pay for a completly new database and
we have to integrate with this existing model having composite key for some
tables. In this case juste because you have an existing model I can't close
'massive' to not support composite key. I like massive and we use already in
concrete applications.
You know in many project you can't control everything and you can't control
some choice. Providing the support to multiple key just allow to solve these
limit situations.

Regards
Angelo Pacifico

2011/6/19 robconery <
reply@reply.github.com>

There are a lot of changes here. I've had this discussion with others
(using SubSonic) with respect to composite keys and to be honest - that's
more code than I'd like to use to support what I consider an edge case (and
not a terribly good database design outside of many to many joins)

Reply to this email directly or view it on GitHub:
robconery#50 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment