[
http://tracker.firebirdsql.org/browse/CORE-5257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vlad Khorsun reopened CORE-5257:
--------------------------------
Fix Version/s: 3.0.2
Re-opened due to wrong parsing of nested keys
> Enable nested keys in plugin configuration
> ------------------------------------------
>
> Key: CORE-5257
> URL: http://tracker.firebirdsql.org/browse/CORE-5257
> Project: Firebird Core
> Issue Type: Improvement
> Components: API / Client Library, Engine
> Affects Versions: 3.0.0
> Reporter: Vlad Khorsun
> Assignee: Vlad Khorsun
> Priority: Minor
> Fix For: 4.0 Alpha 1, 3.0.2, 3.0.1
>
>
> Config-parsing code already supports nested keys but this feature is
> explicitly disabled in code for more than one nesting level.
> API also supports nested keys, see IConfigEntry::getSubConfig method.
> It seems we could safely enable this feature (and there is users asking for
> it)
> Example of nested keys (could be used in plugins.conf):
> Config = MyPluginConfig {
> Key1 = Val1
> Key2 = Val2 {
> SubKey = Val
> Subkey2 = {
> ...
> }
> }
> }
> currently, such configuration is parsed as set of plain keys.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
