← Back to team overview

maria-discuss team mailing list archive

Re: MariaDbConnector 1.x -> 2.6, problem updating/inserting Torque objects


Hi Eric,
first of all: thx for the ultra fast reply

> configuration variable
we've got the options "at hand". Hence we could add "enforceUpdatableResultSet" (per default false) to Options and then
> new MariaDbResultSetMetaData(columnsInformation, options, forceAlias, options.enforceUpdatableResultSet )

Still feels like a very "localized solution"

-----Ursprüngliche Nachricht-----
Von: Eric Herman <eric.herman@xxxxxxxxx> 
Gesendet: Dienstag, 21. Juli 2020 07:43
An: Clemens Wyss - MySign AG <clemens.wyss@xxxxxxxxx>; maria-discuss@xxxxxxxxxxxxxxxxxxx
Betreff: Re: [Maria-discuss] MariaDbConnector 1.x -> 2.6, problem updating/inserting Torque objects

On 7/21/20 6:39 AM, Clemens Wyss - MySign AG wrote:

> I could patch org.mariadb.jdbc.internal.com.read.resultset. 
> SelectResultSet# getMetaData to  return
>> new MariaDbResultSetMetaData(columnsInformation, options, forceAlias, 
>> false )
> instead of
>> new MariaDbResultSetMetaData(columnsInformation, options, forceAlias, 
>> true )
> but that doesn't really feel "right" 😉

I agree, that doesn't feel "right" ... yet, a patch could be a reasonable short-term work-around, until a better solution becomes apparent.

I would recommend patching such that the boolean value is pulled from a configuration variable if present, otherwise defaults to the current value. In this way, your patch may even be something which you could contribute, as it may turn out to be useful for others.

Eric Herman
mobile:+31 620719662 skype:eric_herman jabber:eric.herman@xxxxxxxxx

Follow ups