Brian,
On 18 Mar 2010, at 18:28, Brian Aker wrote:
Hi!
I'd like to start tracking user ownership on objects, aka who made
what. This is a little more complex for us since we don't have an
internal concept of a "user" since we delegate authority to other
systems. What I am thinking at the moment though is that we set up a
domain:user combination similar to what we see with HTTP. The other
option, and hold onto your socks, would be to use openID identifiers.
I believe we could easily map OpenID to the more traditional systems
like LDAP/etc.
Thoughts?
Why ?
Does this fit into the "lightweight database for the cloud" or
whatever the general plan is.
It does not seem to fit into that description from what I can tell.
I am not opposed in general to the concept, but I think that there
should be some sort of "test" to see if something really fits in or if
it just suits a programmers desires.
So ... how does this fit in, Why does drizzle need or want this ?
It sounds like it might introduce more issues than it solves.
Suppose I clone a database or restore from a backup, who "owns" those
objects now ?
Suppose I have a triggered event or some programatic creation or
cloning of objects.. who owns them ?
Regards,
Tom Hanlon
Cheers,
-Brian
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
Tom Hanlon
[email protected]
Cloudera Certified Hadoop Developer
Certified MySQL DBA
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
