Although I bought ElevateDB when it first came out I have only just
started looking at it and have a lot of catching up to do.

With my DBISAM C/S applications I had a generic user for logging in and
had a Users table to control user access.  In ElevateDB I'd like to use
the built-in user and roles facilities.  However, in the previous Users
tables I stored more than just the username and password, eg.
preferences, cell/mobile no, etc.  If I create a table in the database
to store this additional information, is there some way I can associate
the records with specific users?  For example, does each user have sort
of record ID?

Regards,

SteveG

Steve,

This is how I'm using built-in users in my applications:

-I use the "Name" column in Configuration.Users as an user ID - it's the
primary key in a "UsersData" table inside my databases.

-The only relevant information saved in EDB Configuration database is the
password, everything else is in "UsersData".

-The "Description" column (in Configuration.Users) only gets initialized
with the users's complete name when the user is first created and completely
ignored after that.

-If the application is the only one using the Configuration File, then the
app creates and deletes users in EDB as needed to keep "UsersData"
synchronized with Configuration.Users; if not, i.e. if the same
Configuration File is shared by more than one application, then applications
can only create users (if they don't exist already) in Configuration.Users
but NEVER deletes them.

--
Fernando Dias
[Team Elevate]

Fernando

>>the app creates and deletes users in EDB as needed to keep "UsersData" synchronized with
Configuration.Users

Does this work for you in a "live" situation ? I tried something similar, but I
experienced freezes when adding/altering/dropping users when more than one user is logged on.

Heiko

Heiko,

<< Does this work for you in a "live" situation ? I tried something similar,
but I experienced freezes when adding/altering/dropping users when more than
one user is logged on. >>

This may be related to your other issue.  Altering or dropping a user only
requires an exclusive lock on the user being altered or dropped, and open
locks (shared/exclusive) use very short wait times before issuing an
exception.  This means that any major delay in your case must be an issue
with a configuration write lock, which will take a long time to return with
an exception because it expects to complete since nothing in EDB ever holds
a configuration read or write lock for more than a few milliseconds.  This
sounds very similar to the issue that you're having with catalog read/write
locks failing.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Fernando,

> This is how I'm using built-in users in my applications:
>
> -I use the "Name" column in Configuration.Users as an user ID - it's the
> primary key in a "UsersData" table inside my databases.
>
> -The only relevant information saved in EDB Configuration database is the
> password, everything else is in "UsersData".
>
> -The "Description" column (in Configuration.Users) only gets initialized
> with the users's complete name when the user is first created and completely
> ignored after that.
>
> -If the application is the only one using the Configuration File, then the
> app creates and deletes users in EDB as needed to keep "UsersData"
> synchronized with Configuration.Users; if not, i.e. if the same
> Configuration File is shared by more than one application, then applications
> can only create users (if they don't exist already) in Configuration.Users
> but NEVER deletes them.

Thanks.  So if you need to rename a user, you delete them and then
recreate them, and then change their name in the UsersData table?

Regards,

SteveG

Heiko,

Not that I'm aware of, no

--
Fernando Dias
[Team Elevate]

Steve,

> Thanks.  So if you need to rename a user, you delete them and then
> recreate them, and then change their name in the UsersData table?

My user IDs can't be changed. Once a user is created, all his data can
change except his ID (that is "Name" in EDB Configuration); so yes, the
only way to get a different user ID is to delete the user and recreate him.

--
Fernando Dias
[Team Elevate]