Having user/client centric credential repositories would mean that effecitvely there is NO access control for the centralized resource, because anyone can make up their own user table and connect. (Which is why it's not done like that) The database mechanism for that would be to create separate Databases that each have their own credential repositories.
If there are shared tables - You can control access to particular rows within the tables using views, permissions, parametrized queries (With application enforced values). I think we still need more context / goal to be able to help. On Jul 5, 12:40 am, CoreDXL <[email protected]> wrote: > sorry about my description. I have java desktop application that will > connect over tcp server to the database. I need to connect to the > database with my own user table that has username and password columns > instead of h2's user table. I don't know how I can explain much more > detailed. > > example: first table Employee has username and password columns > second table employer has username and password columns. > while I have these tables I dont wanna use h2's user table to connect > to the database. > I hope this is understandable. I have never used database so I dont > know how I can do that. Is it possible? -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
