Hi Olivier, I attached a patch reducing the sizes of jdbc configuration store table names to JIRA QPID-8214. I only tested it against Derby and MariaDB. I do hope it should work with Oracle as well.
Kind Regards, Alex On 27 June 2018 at 13:32, VERMEULEN Olivier <[email protected]> wrote: > Thanks Alex. > QPID-8214 created. > > Olivier > > -----Original Message----- > From: Oleksandr Rudyy <[email protected]> > Sent: mercredi 27 juin 2018 12:04 > To: [email protected] > Subject: Re: [Broker-J] JDBC configuration store with Oracle > > Hi Olivier, > > Please raise an improvement JIRA about it. I'll try to look into it. > > Kind Regards, > Alex > > On 26 June 2018 at 12:33, VERMEULEN Olivier <[email protected]> > wrote: >> Hello, >> >> I have a problem with the 'JDBC' configuration store when using Oracle. >> In this mode the Broker creates a table named >> 'QPID_CONFIGURED_OBJECT_HIERARCHY'. >> The problem is that this name is already 32 characters long while Oracle >> (before version 12c R2) has a limit of 30 characters. >> Would it be possible to shorten the name of the table? enough to also be >> able to use the table name prefix feature... >> >> Thanks, >> Olivier >> >> ******************************* >> >> This e-mail contains information for the intended recipient only. It may >> contain proprietary material or confidential information. If you are not the >> intended recipient you are not authorised to distribute, copy or use this >> e-mail or any attachment to it. Murex cannot guarantee that it is virus free >> and accepts no responsibility for any loss or damage arising from its use. >> If you have received this e-mail in error please notify immediately the >> sender and delete the original email received, any attachments and all >> copies from your system. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] For additional > commands, e-mail: [email protected] > > ******************************* > > This e-mail contains information for the intended recipient only. It may > contain proprietary material or confidential information. If you are not the > intended recipient you are not authorised to distribute, copy or use this > e-mail or any attachment to it. Murex cannot guarantee that it is virus free > and accepts no responsibility for any loss or damage arising from its use. If > you have received this e-mail in error please notify immediately the sender > and delete the original email received, any attachments and all copies from > your system. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
