Great ! Thanks a lot Alex !

-----Original Message-----
From: Oleksandr Rudyy <[email protected]>
Sent: vendredi 7 février 2020 14:54
To: [email protected]
Subject: Re: [Broker-J] Add support for SQL Server to JDBC store

HI Olivier,
I raised a release JIRA QPID-8410 with an intention to cut the release either 
today or over the weekend.

Kind Regards,
Alex

On Thu, 6 Feb 2020 at 20:51, VERMEULEN Olivier <[email protected]>
wrote:

> Hello,
>
> I see that my pull-request has been approved, great.
> When will be the next release of the Broker-J ?
> We have a client asking for this SQL Server support and they are a bit
> pushy...
>
> Thanks,
> Olivier
>
> -----Original Message-----
> From: Rob Godfrey <[email protected]>
> Sent: mercredi 29 janvier 2020 10:33
> To: [email protected]
> Subject: Re: [Broker-J] Add support for SQL Server to JDBC store
>
> Hi Olivier,
>
> as long as there are no requirements for code with incompatible
> licenses to be distributed by the Broker (which there shouldn't be) I
> don't see any issues at all (basically this is the same as supporting
> one of the other proprietary database vendors).
> Given their common roots, I assume the SQL server configuration will
> be mostly similar to the Sybase configuration (I think I may even have
> tested this many many years ago).
>
> -- Rob
>
> On Wed, 29 Jan 2020 at 09:47, VERMEULEN Olivier <
> [email protected]>
> wrote:
>
> > Hello,
> >
> > We would like to contribute the support of SQL Server by the
> > Broker-J JDBC store.
> > But before doing the dev I just wanted to make sure that there is no
> > restrictions on your side?
> >
> > 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 authorized 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.
> >
> *******************************
> 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 authorized 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.
>
*******************************
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 authorized 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]

Reply via email to