|Best way to work around errorsin the DbDefinitions [message #49978]
||Thu, 18 September 2008 22:24
| Philipp Simon
Registered: July 2009
We are currently using the DataBasedefinitions from enablement a lot. What
happened now is that we e.g. in the DB2 zSeries one met some inaccurate
information such as CHAR FOR SDBS DATA datatype missing or ROWID one
beeing nullable. Waiting for a bugfix on the one hand takes time and on
the other hand the new version might not make it into our target platform.
So i was wondering what you would think is the best way to solve problems
like that ( besides fixing the dbdefinitions xmi file). My best guess
would be to create some sort of layer around the dbdefinition and fix the
inaccuracies there with some ugly if else equals code. Any better ideas (
like is it possible to add /overwrite parts of these dbdefinitons by e.g.
adding a supplemental xml file via an extension point ? ).
Powered by FUDForum
. Page generated in 0.01937 seconds