Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

service call for write aliases.conf [CORE1422] #1840

Open
firebird-automations opened this issue Aug 21, 2007 · 4 comments
Open

service call for write aliases.conf [CORE1422] #1840

firebird-automations opened this issue Aug 21, 2007 · 4 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: Laszlo Moravecz (eMeL) (emel)

Votes: 2

If I create a database I should like register it immediately.

If my program run as a remote client or the logged user have not enought right to FB directory need some help :)
A new service call can make it ;)

I think it need keep to some rule:

- If path part of new registration no point to a database file: return an error.
- If this is a new alias name, simple write it.
- If this is a existent alias name:
-- If it point to same path: do nothing.
-- If it point to an existent path: return an error.
-- If it point to a dead (no valid) path: overwrite it.

This new service function don't break security measure, but give chance: if you can create database you can register it!

What a benefit of FB? You don't need person for admin it!
Why you need write aliases.conf by hand against program code?

@firebird-automations
Copy link
Collaborator Author

Modified by: Laszlo Moravecz (eMeL) (emel)

description: If I create a database I should like register it immediately.

If my program run as a remote client or the logged user have not enought right to FB directory need some help :)
A new service call can make it ;)

I think it need keep to some rule:

- If path part of new registration no point to a database file: return an error.
- If this is a new alias name, simple write it.
- If this is a existent alias name:
-- If it point to same path: do nothing.
-- If it point to an existent path: return an error.
-- If it point to a dead (no valid) path: overwrite it.

This new service function don't break security measure, but give chance: if you can create database you can register it!

What a benefit of FB? We don't need person for admin it!
Why you need write aliases.conf by hand against program code?

=>

If I create a database I should like register it immediately.

If my program run as a remote client or the logged user have not enought right to FB directory need some help :)
A new service call can make it ;)

I think it need keep to some rule:

- If path part of new registration no point to a database file: return an error.
- If this is a new alias name, simple write it.
- If this is a existent alias name:
-- If it point to same path: do nothing.
-- If it point to an existent path: return an error.
-- If it point to a dead (no valid) path: overwrite it.

This new service function don't break security measure, but give chance: if you can create database you can register it!

What a benefit of FB? You don't need person for admin it!
Why you need write aliases.conf by hand against program code?

@firebird-automations
Copy link
Collaborator Author

Commented by: Laszlo Moravecz (eMeL) (emel)

Methods:

* Only SYSDBA or Database Owner (of database in path) can call this service.

----------------------------------------------------------------------------------------------------------

Reasons:

When you create a database, immediatly [together] must register it.
We shouldn't use database path in client.
If I can create database in client, I _must_ register it from client application.

----------------------------------------------------------------------------------------------------------

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Workflow: jira [ 12862 ] => Firebird [ 15331 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: Pabloj (pabloj_sourceforge)

Should be in the SQL interface, CREATE ALIAS 'alias_name' FOR 'database' DROP and ALTER too

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant