Solomon, thank you for your additional insights. Of course we'll have to wait
for SQL Server 2019 to be adopted - tactful devops wait for SP2 of v4 to
change from v2 to v3 :-)
Indeed I solved the problem in NVARCHAR / NCHAR / NTEXT by adding the method
WideString>>#glorpPrintSQLOn: which is almost
eftomi wrote
> I found the "ultimate" place where strings are being preparedfor INSERT
> INTO clause - this happens in String>>#glorpPrintSQLOn:. Not soeasy to
> parametrize at a first glance. Maybe withWideString>>#glorpPrintSQLOn: but
> I'm not sure how other platforms would behappy.An interestin
Thanks, Sven. I found the "ultimate" place where strings are being prepared
for INSERT INTO clause - this happens in String>>#glorpPrintSQLOn:. Not so
easy to parametrize at a first glance. Maybe with
WideString>>#glorpPrintSQLOn: but I'm not sure how other platforms would be
happy. I decided to wo
Hi Tomaz,
> On 11 Oct 2019, at 18:15, eftomi wrote:
>
> Dear all,
>
> I'm working on ADO database driver for Glorp by using Pablo's PharoCOM. The
> structure of the driver is similar to Sven's P3DatabaseDriver and P3Client
> (thanks, Sven for very clear architecture :-) ) and the work is progre
Dear all,
I'm working on ADO database driver for Glorp by using Pablo's PharoCOM. The
structure of the driver is similar to Sven's P3DatabaseDriver and P3Client
(thanks, Sven for very clear architecture :-) ) and the work is progressing
quite nicely. I can connect to SQL Server, PostgreSQL and cre
