[MAGNOLIA-3108] On Windows only: Changing property name of characters to lower/upper case results in disappearing property Created: 05/Mar/10  Updated: 05/Mar/10  Resolved: 05/Mar/10

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 3.6.3
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Christian Ringele Assignee: Christian Ringele
Resolution: Workaround exists Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows 2003 Server
MySQL 5.1
Magnolia 3.6.3
JCR 1.4.5 core
PM: jackrabbit-mysql-search.xml (simple PM)


Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

When changing characters of a property's name to lower/upper case, the property disappears:

  • Change property in JCR from 'test' to 'TEST'
    The property disappears and is not stored anymore in MySql.

The same happens when adding a second propert with the same name, just having different character in lower/upper case:

  • add property 'test'
  • add property 'TEST'
    -> 'test' remains and 'TEST' disappears


 Comments   
Comment by Christian Ringele [ 05/Mar/10 ]

First deleting the property and then adding it again with the new name works.
Is a bit cumbersome, but worked to resolve the problem.

Comment by Christian Ringele [ 05/Mar/10 ]

Another work around is switching to the PM: jackrabbit-bundle-mysql-search.xml

For that a export/import of the data has to be done between the PM switching.

Generated at Mon Feb 12 03:43:16 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.