I'm in favor of the status quo. It's useful to have them available out of the box to be able to pick the one you need and proceed without having to look elsewhere. The same goes for the fieldtype definitions.
Regards Scott On 8/01/2018 6:26 AM, "Pierre Smits" <pierresm...@apache.org> wrote: We could consider having example configurations (entityengine.xml files) for applicable database solutions in the documentation (in confluence). Removing unused code snippets is always worth the effort put forward. Best regards, Pierre Smits V.P. Apache Trafodion On Sun, Jan 7, 2018 at 5:36 PM, jler...@apache.org <jler...@apache.org> wrote: > Le 07/01/2018 à 11:43, Jacques Le Roux a écrit : > >> My answer to your question is: we should keep them of course, except if a >> better way would be proposed, I see none for now... >> > I must have said: I see none PROVIDED for now... > > We could consider a modular solution which would include split parts of > the file in the remaining main, but I'm not sure it's worth it >
