Hi!

I can create more sessions. But interesting, if I create a new local session, and I want to open it, I got error - login
problems.

In PGAdmin I have many registrations (collect "configs" - databases to manage):
http://i.justrealized.com/media/2008/10/using-pgadmin-iii-for-postgresql.jpg

PGAdmin is not change the "DataBases config" (pgdb), only I can collect all databases that I want to manage.
This is very useul, when you want to change more of them, you can easily select, open, or copy datas between them.

As I see the EDBAdmin is different than this.

I need to set "Default sessions path" for every operation what I want to do in any DataBase (to set config file).

Possible it would be better, if EDBManager can used with parameters, like "Open" (like Word, AR, dbsys).
For example: when I associate config file with EDBManager, and I clicked on a config file, the Default Session path
automatically set, and Session opening.

This would be better when I not need to close session/edit session/set path/reopen session...

Or if is supports to set more local session and I can registered more databases, and it would be good.

Why I got login problem in the second session I want to create?

<< I can create more sessions. But interesting, if I create a new local
session, and I want to open it, I got error - login
problems. >>

You have to define the user ID and password to use for a given session, or
else you will receive a login dialog when you try to connect.  But, more
importantly, you shouldn't need to create more than one session.

<< PGAdmin is not change the "DataBases config" (pgdb), only I can collect
all databases that I want to manage.
This is very useul, when you want to change more of them, you can easily
select, open, or copy datas between them. > As I see the EDBAdmin is
different than this. >>

No, it's exactly the same - you can have up to 4096 databases defined in a
given configuration.  You only need one local session to work with all of
the databases that are defined in the configuration.

<< I need to set "Default sessions path" for every operation what I want to
do in any DataBase (to set config file). >>

No, you don't.  Just define all of the databases using the same session, and
you'll be all set.  You can even just use the Default session that is
pre-defined for you.

The key is:

Sessions <> databases

Sessions <> configuration

Session are simply a virtual construct that allows you to work with a given
configuration, whether it is on an EDB Server, or a local configuration.

--
Tim Young
Elevate Software
www.elevatesoft.com

durumdara

>Why I got login problem in the second session I want to create?

What was the error message?

Roy Lambert [Team Elevate]

Roy Lambert wrote:

<<durumdara
>Why I got login problem in the second session I want to create?
What was the error message?
Roy Lambert [Team Elevate]>>
---------------------------
ElevateDB Manager
---------------------------
ElevateDB Error #501 Login failed (The maximum number of login attempts has been exceeded)
---------------------------
OK   
---------------------------

With default password I can use it, and I can create a new user with new password. Caps Lock locked...
Sorry...

Thanks:
  dd

"Tim Young [Elevate Software]" wrote:
<< I need to set "Default sessions path" for every operation what I want to
do in any DataBase (to set config file).

No, you don't.  Just define all of the databases using the same session, and
you'll be all set.  You can even just use the Default session that is
pre-defined for you.

The key is:
Sessions <> databases
Sessions <> configuration
Session are simply a virtual construct that allows you to work with a given
configuration, whether it is on an EDB Server, or a local configuration.>>>

Hi!

The main problem that users/roles and DB names are defined in the config.

1.) Users

Later we want to use "users" in edb. Now we have user.dat that keep the login information.

But we want to change, because we better see in server log if users using their own names. We can filter what user
cause the problem (somewhere IP's are dynamic).

When I have two config, a global to manage (one only), and one in the app dir (to simulate real site), possible I miss
something in the debug.

For example: I set new role in global config; but I forget to reflect in the test config of the application...
(So we place conf files in the folder where exe file exists).

2.) DB Names

Now we uses same DB name in our customers, for example "XDB".
When we use global config, we need to set diff. names for databases.
Because app's config hold only this XDB, but global config cannot hold more XDB's with diff. paths...
May we need to change db names...

Thanks:
  dd

durumdara

>With default password I can use it, and I can create a new user with new password. Caps Lock locked...
>Sorry...

Not a problem - my favourite is when the numlock has been turned off

Roy Lambert

<< When I have two config, a global to manage (one only), and one in the app
dir (to simulate real site), possible miss something in the debug. >>

Why are you using two different configuration files for the same application
?  I wouldn't recommend this.  You should have one configuration file per
application.

Think of a configuration file as a "master" database.  You don't have more
than one master database in SQL Server - you have one, and that one master
database determines which databases are available, as well as how the users
and roles are defined.  ElevateDB is the same way.

--
Tim Young
Elevate Software
www.elevatesoft.com

durumdara

>The main problem that users/roles and DB names are defined in the config.
>
>1.) Users
>
>Later we want to use "users" in edb. Now we have user.dat that keep the login information.
>
>But we want to change, because we better see in server log if users using their own names. We can filter what user
>cause the problem (somewhere IP's are dynamic).
>
>When I have two config, a global to manage (one only), and one in the app dir (to simulate real site), possible I miss
>something in the debug.
>
>For example: I set new role in global config; but I forget to reflect in the test config of the application...
>(So we place conf files in the folder where exe file exists).

My approach to this is I've moved the password out of my users table (I also renamed it to Staff to reduce my confusion) into ElevateDB. Now when someone logs in they first log into ElevateDB and then if that's successful get their entry from the Staff table where all their personalised configuration data is kept (eg screen colours) and only if that's successful as well are they allowed to access the app.

>2.) DB Names
>
>Now we uses same DB name in our customers, for example "XDB".
>When we use global config, we need to set diff. names for databases.
>Because app's config hold only this XDB, but global config cannot hold more XDB's with diff. paths...
>May we need to change db names...

Are you hosting your customers, if not and the database is on their own site you'll only have one XDB per configuration. Can you explain more about the "global config" what is it? what is it used for? what does it contain?

Roy Lambert [Team Elevate]

Dear Tim!

"Tim Young [Elevate Software]" wrote:
<< When I have two config, a global to manage (one only), and one in the app
dir (to simulate real site), possible miss something in the debug.

Why are you using two different configuration files for the same application
?  I wouldn't recommend this.  You should have one configuration file per
application.>>

You suggested this:
  No, it's exactly the same - you can have up to 4096 databases defined in a
 given configuration.  You only need one local session to work with all of
 the databases that are defined in the configuration.
 No, you don't.  Just define all of the databases using the same session, and
 you'll be all set.  You can even just use the Default session that is
 pre-defined for you.

<<Think of a configuration file as a "master" database.  You don't have more
than one master database in SQL Server - you have one, and that one master
database determines which databases are available, as well as how the users
and roles are defined.  ElevateDB is the same way.>>

I understand it, but I have 3 ways to manage/develop our customers database.

A.)
We put the config file to application.exes' folder. This points to DB, named "XDB" (default name of dbs).
We use Default Session in manager, and set the path manually for each when needed.
(It would be faster with association in manager with this code:
OnAppstart:
 if ParamCount > 1 then begin
    CloseSession('Default');
    SetSessionPath('Default', ExtractFileDir(ParamStr(1));
    OpenSession;
 end;

B.)
We use separated manager's Session for each of the customers.
This allow us (as in A. option) to choose same name (XDB) for each customer's database, and because of separation we can define another
users/roles for each customers (to make the tests).

C.)
We rename databases:
XDB_[CUstomerName1], XDB_[CUstomerName2] ...
We use one global config file placed in "c:\dev\" for manager.
Manager have only "Default Session", and all customer's database placed in it.
But for application testing we have configs for each databases, placed near to application.exe-s.

This problematic, because:
1.) Configs may be different (global manager (Default), and application configs)
2.) User/Roles are same for all.
3.) Renamed databases.

So if possible, we don't want to use option C.), and A.) option is slow and uncomfortable. B.) Seems to be good.

I don't know, is it understandable? May I don't explain it good...

Thanks:
  dd

>B.)
>We use separated manager's Session for each of the customers.
>This allow us (as in A. option) to choose same name (XDB) for each customer's database, and because of separation we can define another
>users/roles for each customers (to make the tests).


This is the way to go.

Roy Lambert [Team Elevate]