Page 1 of 1

Bug?: SYSDBA Network Read-only not working

Posted: Sat Sep 25, 2021 8:01 pm
by MetalDrop
Not sure if this is a bug or by design.

When logged into a network database as SYSDBA read-only doesn't work.
- The read only icon is grayed out and read-only appears to have zero effect.

Re: Bug?: SYSDBA Network Read-only not working

Posted: Tue Sep 28, 2021 10:21 am
by admin
I'm unable to reproduce this. Which type of data are we talking about? Was that a regular user who marked an item as read-only?

Re: Bug?: SYSDBA Network Read-only not working

Posted: Tue Sep 28, 2021 6:45 pm
by S_Belle
I can reproduce this.

I only use the SYSDBA user on my network database since I'm the only users, and can confirm that read-only doesn't work with the SYSDBA account.

Since I don't use any normal users obviously all items I tested were created by and marked as read-only by the SYSDBA account, and SYSDBA can still write to the notes it's marked as read-only.

Re: Bug?: SYSDBA Network Read-only not working

Posted: Tue Sep 28, 2021 8:22 pm
by admin
I think this issue might be database-dependant. Please create a new one and see if the problem will be reproducible with it. If so, forward me the db. Thanks!

Re: Bug?: SYSDBA Network Read-only not working

Posted: Wed Sep 29, 2021 3:04 am
by MetalDrop
I made a new database and it worked fine, then I thought about favorites breaking in the beta when the database got above 1,000 notes.

So I duplicated a note to over 1,000 and tried again and sure enough read-only was broken with SYSDBA again.

So much like the favorites issue this one seems to be related to something that breaks after the database gets some number of note entries.

I've attached a database with a bunch of blank notes and one note that is marked as read-only that can be edited when logged in as SYSDBA on a network.

Re: Bug?: SYSDBA Network Read-only not working

Posted: Wed Sep 29, 2021 10:51 am
by admin
This is by design. In Business edition you mark an item as read-only for other users, not for yourself. We will fix the inconsistency described in you last post. Thanks!