Libelektra: Xerces: Problems with INI as Default Storage

[sanssecours]

Steps to Reproduce the Problem

1. Configure Elektra with INI as default storage

   mkdir build
   cd build
   cmake .. -GNinja -DPLUGINS='ALL' -DKDB_DB_FILE='default.ini' -DKDB_DB_INIT='elektra.ini' -DKDB_DEFAULT_STORAGE=ini
   

2. Build Elektra

   ninja
   

3. Run the following commands:

   sudo kdb mount xerces.xml /examples/xercesfile xerces
   
   kdb set /examples/xercesfile foo
   kdb setmeta /examples/xercesfile xerces/rootname xerces
   kdb set /examples/xercesfile/bar bar
   kdb setmeta /examples/xercesfile/bar meta "da_ta"
   
   kdb getmeta /examples/xercesfile xerces/rootname
   #> xerces
   
   kdb get /examples/xercesfile/bar
   #> bar
   
   kdb export /examples/xercesfile xerces
   

Expected Result

#> <?xml version="1.0" encoding="UTF-8" standalone="no" ?>
#> <xerces>
#>
#>   <bar meta="da_ta">bar</bar>foo
#>
#> </xerces>

Actual Result

# ERROR: 174

Error Message

Sorry, the error (#174) occurred ;(
Description: general xml error
Reason: invalid or illegal XML character
Ingroup: plugin
Module: xerces
At: ../src/plugins/xerces/xerces.cpp:114
Mountpoint: /examples/xercesfile
Configfile: /dev/stdout

System Information

• Elektra Version: master

[markus2330]

Thank you for reporting! Good that we did not switch to INI as default in this release.

I used 0.8.21 as milestone: for the lcdproc release INI as default is desirable. In general you do not have to tag bugs as "1.0.0", it is clear that we want to release non-experimental parts of 1.0.0 without known bugs. Having too many issues for "1.0.0" makes the goal less clear. We could add another milestone for your purpose?

[sanssecours]

We could add another milestone for your purpose?

How about 0.9? I think 1.0 should only fix minor issues of an almost stable 0.9.x release.

[markus2330]

Good suggestion, I created 0.9.0.

INI-specific bugs, however, are 0.8.21, unless you plan to create a new INI plugin which we can use as default?

[sanssecours]

INI-specific bugs, however, are 0.8.21, unless you plan to create a new INI plugin which we can use as default?

Nope 😊. I think it makes more sense to fix the already existing INI plugin, instead of creating a new one, containing new additional bugs.

[markus2330]

This is now low-priority thus we do not have INI as default.

[stale[bot]]

I mark this issue stale as it did not have any activity for one year. I'll close it in two weeks if no further activity occurs. If you want it to be alive again, ping the issue by writing a message here or create a new issue with the remainder of this issue.
Thank you for your contributions :sparkling_heart:

[stale[bot]]

I closed this issue now because it has been inactive for more than one year. If I closed it by mistake, please do not hesitate to reopen it or create a new issue with the remainder of this issue.
Thank you for your contributions :sparkling_heart: