On 2017-04-28 13:33, Julian Reschke wrote:
On 2017-04-28 13:15, Davide Giannella wrote:
...
However, if you select all RDB profiles you'll include essentially all
JDBC drivers, in which case maintaining the limit becomes pretty
pointless...
I'd say you could change the size for the RDB profiles only (adding the
enforcer size under the profiles) or simply increase the general size.
I can try that, but it won't work that well because then we have
multiple related settings in different places, and it also doesn't work
well when multiple RDB profiles are used.
It seems strange to me that we're not embedding the jdbc dependencies
for the released jar. Maybe we want to change that and simplify.
For 7 different databases? Also, what about those drivers which are not
open-source?
How bit is the generated jar for the RDB profiles?
Derby, for instance, is ~3MB (that includes the DB). The PostgreSQLJDBC
driver is ~700K.
Best regards, Julian
So, can we minimally have a way to either override the value per command
line, or to skip the check?
Best regards, Julian
