Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Dynamic component configured at run-time issue with keys with the same prefix

Description

In my application I map an attributes collection (IDictionary) at run-time to every entity mapped to the database. This allows me to add additional fields across different modules. I have recently upgraded from version 3.3.4 to 4.1.1 and I have found that this is broken if the fields have the same prefix.

This is a critical issue for me as my application is heavily built around the concept of modularity and allowing third party developers to add additional functionality on top of any entity mapped to the database.

Environment

None

Activity

Show:

Alex Zaytsev 
June 1, 2017 at 10:38 PM

You need to add column to a table as well. (This is usually done by a "binder").

Alex Zaytsev 
June 1, 2017 at 10:30 PM

Marked as trivial, as this is for an unusual case where user adds columns to a mapping at runtime.

Lee Timmins 
May 3, 2017 at 8:31 AM

Frédéric Delaporte 
May 3, 2017 at 8:21 AM

Your test cases can still be merged with a PR. Just put an [Ignore("Not fixed yet")] on them.

Lee Timmins 
May 3, 2017 at 7:45 AM

Thanks Alexander. For now I have just overridden the MaxAliasLength and it works fine. Maybe the default value could be increased as a quick workaround? I'm not to familiar with the underlying code and I'm sure there's a better solution so I won't attempt a pull request.

Won't Fix

Details

Assignee

Reporter

Labels

Components

Affects versions

Priority

Who's Looking?

Open Who's Looking?
Created May 2, 2017 at 12:15 PM
Updated June 1, 2017 at 10:38 PM
Resolved June 1, 2017 at 10:38 PM
Who's Looking?