You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I downloaded ibpp from http://www.ibpp.org and compiled the tests project using VC6.
When running it from debug mode, Test1-Test5 was ok.
However Test6() raisied the following exception:
From Test6(),
// Connecting two users
db1 = IBPP::DatabaseFactory(ServerName, DbName, "EPOCMAN", "test");
db1->Connect();
IBPP::Database db2 = IBPP::DatabaseFactory(ServerName, DbName, UserName, Password);
db2->Connect();
// Checking their names
std::vectorstd::string\ usernames;
db1->Users(usernames);
if (usernames.size() != 2)
{
_Success = false;
printf(_(" Expected 2 users connected, found %d.\n"), (int)usernames.size());
}
printf(" Connected users : ");
for (unsigned int i = 0; i < usernames.size(); i++)
{
printf("%s", usernames[i].c_str());
if (i < usernames.size()-1) printf(", ");
}
printf("\n");
The above code seems to expect to get two users, but
usernames.size() returned 1, not 2 and.
Is this normal?
I haven't changed anything from the tests project at all.
Olivier Mascia from ibpp said:
FB2.5 changed a lot of semantic details about user management and reporting. The old reporting method (calling isc_database_info with a resquest for isc_info_user_names) might not return all connected users anymore, might return them all except the current one running the query, or might have a minor bug - compared to previous FB versions).
Please confirm if FB2.5 changed that way compared to previous FB versions.
thx
HaeRim
The text was updated successfully, but these errors were encountered:
isc_database_info( isc_info_user_names ) will return
a) current user name only, if
- you run CS\SC, or
- you are not SYSDBA and not an owner of database
b) all attached user names if you run SS AND you are SYSDBA (or owner)
this behavior is very old and not new for v2.5.
---
Olivier Mascia from ibpp said:
FB2.5 changed a lot of semantic details about user management and reporting. The old reporting method (calling isc_database_info with a resquest for isc_info_user_names) might not return all connected users anymore, might return them all except the current one running the query, or might have a minor bug - compared to previous FB versions).
---
This is very strange to hear, especially "might return them all except the current one running the query". I never heard such complains.
Again, this ticket looks like attempt to get support which should be done using support list.
Submitted by: HaeRim Lee (ehaerim)
I downloaded ibpp from http://www.ibpp.org and compiled the tests project using VC6.
When running it from debug mode, Test1-Test5 was ok.
However Test6() raisied the following exception:
From Test6(),
// Connecting two users
db1 = IBPP::DatabaseFactory(ServerName, DbName, "EPOCMAN", "test");
db1->Connect();
IBPP::Database db2 = IBPP::DatabaseFactory(ServerName, DbName, UserName, Password);
db2->Connect();
// Checking their names
std::vectorstd::string\ usernames;
db1->Users(usernames);
if (usernames.size() != 2)
{
_Success = false;
printf(_(" Expected 2 users connected, found %d.\n"), (int)usernames.size());
}
printf(" Connected users : ");
for (unsigned int i = 0; i < usernames.size(); i++)
{
printf("%s", usernames[i].c_str());
if (i < usernames.size()-1) printf(", ");
}
printf("\n");
The above code seems to expect to get two users, but
usernames.size() returned 1, not 2 and.
Is this normal?
I haven't changed anything from the tests project at all.
Olivier Mascia from ibpp said:
FB2.5 changed a lot of semantic details about user management and reporting. The old reporting method (calling isc_database_info with a resquest for isc_info_user_names) might not return all connected users anymore, might return them all except the current one running the query, or might have a minor bug - compared to previous FB versions).
Please confirm if FB2.5 changed that way compared to previous FB versions.
thx
HaeRim
The text was updated successfully, but these errors were encountered: