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

Provide mechanism to get engine version without needing to call API function [CORE1018] #632

Closed
firebird-automations opened this issue Nov 24, 2006 · 12 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: Sean Leyne (seanleyne)

Is duplicated by CORE1494
Is related to QA112

There have been a number of requests on the Support lists, asking for the ability to determine the engine version without needing to make an API call.

Some suggested implementations which would return the engine version string are:

- Add a new 'virtual' column (RDB$EngineVersion) to the RDB$Database table

- Add a new 'virtual' DSQL (SP/Trigger) variable (EngineVersion)

Commits: d74650a

====== Test Details ======

Engine version could contain more tha one digit in any section or more sections.
Pattern used in SIMILAR_TO for matching such cases of engine version as:
'3.2.23' or '3.3.2.1.0.1.2.3.4.5.7' etc

@firebird-automations
Copy link
Collaborator Author

Commented by: @dyemanov

What should be returned:

- 2.1
- 2.1.0
- 2.1.0.14427
- WI-T2.1.0.14427 Firebird 2.1 Unstable

?

@firebird-automations
Copy link
Collaborator Author

Commented by: Sean Leyne (seanleyne)

If we are talking about "RDB$EngineVersion" then I think "2.1.0" is appropriate.

If we are talking about "RDB$EngineFullVersion" then I think "WI-T2.1.0.14427 Firebird 2.1 Unstable" is appropriate. ;-)

Seriously, as long as the elements of the Version number (2.1.0) are maintained correctly, then that alone should be enough for most developers. The "full string" is a little much.

@firebird-automations
Copy link
Collaborator Author

Commented by: @dyemanov

select rdb$get_context('SYSTEM', 'ENGINE_VERSION') from rdb$database
-- returns: '2.1.0'

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 2.1 [ 10041 ]

assignee: Dmitry Yemanov [ dimitr ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Fix Version: 2.1 Alpha 1 [ 10150 ]

Fix Version: 2.1.0 [ 10041 ] =>

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Link: This issue is related to QA112 [ QA112 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

Link: This issue is duplicated by CORE1494 [ CORE1494 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: Ain Valtin (ain)

I would like to see a solution which doesn't require user to parse some string. See report 1494 for (IMO) better solution. It is easy to concatenate several numbers together into complete version number, but it is much hareder to parse (in SQL!) "x.y.z" to separate numbers.

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Workflow: jira [ 11351 ] => Firebird [ 15422 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @pmakowski

select rdb$get_context('SYSTEM', 'ENGINE_VERSION') from rdb$database
is ok

@firebird-automations
Copy link
Collaborator Author

Modified by: @pmakowski

status: Resolved [ 5 ] => Closed [ 6 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

status: Closed [ 6 ] => Closed [ 6 ]

QA Status: Done successfully

Test Details: Engine version could contain more tha one digit in any section or more sections.
Pattern used in SIMILAR_TO for matching such cases of engine version as:
'3.2.23' or '3.3.2.1.0.1.2.3.4.5.7' etc

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

2 participants