Issue Details (XML | Word | Printable)

Key: CORE-3470
Type: Bug Bug
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: HaeRim Lee
Votes: 0
Watchers: 5
Operations

If you were logged in you would be able to see more operations.
Firebird Core

FB 2.5 do raise an error when attempting to remove a non existing user, while previous versions were silent about that?

Created: 09/May/11 04:24 PM   Updated: 09/May/11 06:02 PM
Component/s: API / Client Library
Affects Version/s: 2.5.0
Fix Version/s: None

Environment: Win XP SP3, Intel(R) Core(TM)2 Quad CPU, Q9400 @ 2.66GHz, 3.5GB RAM


 Description  « Hide
I downloaded ibpp from 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:
 
Test 6 --- Service APIs
              WI-V2.5.0.26074 Firebird 2.5
              Shutdown...
              Validate...
              Restart...
              Sweep...
              Backup...
              Restore...
              Manage users
*** IBPP::SQLException ***
Context: Service::RemoveUser
Message: isc_service_start failed
 
SQL Message : -85
An error occurred while trying to update the securitey database
 
Engine Code : 335544753
Engine Message :
The user name specified was not found in the security database
 
Engine Code : 335544753

I haven't changed anything from the tests project at all.

Olivier Mascia said:

Most probably FB 2.5 do raise an error when attempting to remove a non existing user, while previous versions were silent about that. See line 939: svc->RemoveUser("EPOCMAN"); right after the printf("Manage users");

So does FB2.5 raise an error when attempting to remove a non-existing user, while previous versions do not?

thx
HaeRim


 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Vlad Khorsun added a comment - 09/May/11 06:02 PM
Are you report a bug or just ask a question ?

If first, explain why do you think it is a bug.
If second, use support list.