Closed GoogleCodeExporter closed 9 years ago
The problem is that DataSources do not link back to the original project that
contains it so it cannot check for duplicates.
The problem right now is taken care of at the high level. The config window
checks that if the user is trying to change the name to an existing one and
won't allow it.
Original comment by yuriy.b...@gmail.com
on 21 Nov 2011 at 11:17
I fixed the failing test on this issue. The DataSources don't know about each
other, so it is possible to change one DataSource's name to conflict with
another in the same project. We ensure that this doesn't happen at the
ConfigurationPreferences level, when the user names the change.
In other words, you can create a ProjectPreferences object with two DataSource
objects with the same name. But you cannot do it through Crystal's current
design.
Original comment by yuriy.b...@gmail.com
on 28 Dec 2011 at 7:58
Original issue reported on code.google.com by
yuriy.b...@gmail.com
on 21 Jul 2011 at 9:36