Hi, > That's indeed what is happening and what makes Jackrabbit fail to start. The > case is, however, that for this particular deployment it is preferred to > don't give those rights to the jackrabbit user.
If I understand correctly, the user has read access to the tables, but doesn't have access to read the metadata of its own tables? I didn't know you can do that. I think that's not a valid use case. Such a user couldn't even use regular (SQL) tools to access his own tables. Regards, Thomas
