Ticket #807 (closed task: fixed)
Review the need of OSyncMappingView
| Reported by: | dgollub | Owned by: | dgollub |
|---|---|---|---|
| Priority: | highest | Milestone: | OpenSync 0.40 |
| Component: | OpenSync | Version: | 0.38 |
| Severity: | normal | Keywords: | |
| Cc: |
Description
OSyncMappingView is currently dead code - which gets not build at all. Review the purpose and the need of the code. First impression is some performance enhancement or ongoing refactoring of MappingTables/Engines?.
Change History
comment:1 Changed 3 years ago by dgollub
- Priority changed from normal to highest
- Milestone changed from 0.38 to 0.40
comment:3 Changed 3 years ago by dgollub
- Status changed from new to closed
- Resolution set to fixed
Never got discussed - i recommend to drop OSyncMappingView for now:
- code doesn't get lost, everything is still in SVN
- OSyncMappingView needs to be rewritten anyway with database abstraction
OSyncMappingView got dropped with r4292 view-table gets interesting again with a performance-review after 0.40
Note: See
TracTickets for help on using
tickets.

I would schedule this ticket for dicussion on upcoming developer meeting. highest prio, since this should be quite trivial to side if it got dropped from SVN or not.