Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.clipper.visual-objects > #11756 > unrolled thread
| Started by | Pilks <richardp@lukhozi.co.za> |
|---|---|
| First post | 2018-07-13 08:45 -0700 |
| Last post | 2018-10-30 13:52 -0700 |
| Articles | 12 — 7 participants |
Back to article view | Back to comp.lang.clipper.visual-objects
VO2ADO with MariaDB Pilks <richardp@lukhozi.co.za> - 2018-07-13 08:45 -0700
Re: VO2ADO with MariaDB Pilks <richardp@lukhozi.co.za> - 2018-07-13 08:54 -0700
Re: VO2ADO with MariaDB D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2018-07-14 09:13 +0200
Re: VO2ADO with MariaDB Pilks <richardp@lukhozi.co.za> - 2018-07-16 08:13 -0700
Re: VO2ADO with MariaDB gianluca.pinoli@proximacentauri.it - 2018-07-16 03:19 -0700
Re: VO2ADO with MariaDB Pilks <richardp@lukhozi.co.za> - 2018-07-16 08:10 -0700
Re: VO2ADO with MariaDB Sherlock <sherlock@sherlock.com.au> - 2018-07-14 07:19 -0700
Re: VO2ADO with MariaDB "Wolfgang Riedmann" <wriedmann@gmail.com> - 2018-07-15 07:38 +0200
Re: VO2ADO with MariaDB Pilks <richardp@lukhozi.co.za> - 2018-07-16 08:06 -0700
Re: VO2ADO with MariaDB Pilks <richardp@lukhozi.co.za> - 2018-07-19 08:54 -0700
Re: VO2ADO with MariaDB epremuz@gmail.com - 2018-10-30 13:42 -0700
Re: VO2ADO with MariaDB dlzc <dlzc1@cox.net> - 2018-10-30 13:52 -0700
| From | Pilks <richardp@lukhozi.co.za> |
|---|---|
| Date | 2018-07-13 08:45 -0700 |
| Subject | VO2ADO with MariaDB |
| Message-ID | <18031e71-610c-4b76-a2b1-fff95e27e8f9@googlegroups.com> |
Hi All
Maintaining and old system that uses VO 2.7 and makes use of VO2ADO to connect to a mysql database via ODBC. The server was upgraded to MariaDB recently and all was fine until we upgraded a workstation to Win 10. That person started experiencing problems with rounding of decimal numbers to integers when saving to the database.
I updated the connector to a MariaDB connector and solved that problem.
Now if I pull all fields from a table I get an error for the Win 10 PC on the Execute method call:
// Error message
Error Code: Data provider or other service returned an E_FAIL status.
Subsystem: Vo2Ado
Error SubCode: 16389
The code involved is in the init of a DataWindow:
// sSqlText = "SELECT * FROM projects where project_id='2634'"
SELF:oCmnd := AdoCommand{}
SELF:oCmnd:ActiveConnection := oDMSC // global variable
SELF:oCmnd:CommandText := sSqlText
uRet := SELF:oCmnd:Execute(NIL,NIL,NIL) // Error on this line
I am busy with a translation to XSharp but that is quite a long way off and this problem is immediate.
Anyone with a clue? Maybe a description of the error subcode (16389)?
TIA
Richard
[toc] | [next] | [standalone]
| From | Pilks <richardp@lukhozi.co.za> |
|---|---|
| Date | 2018-07-13 08:54 -0700 |
| Message-ID | <60fc963f-767a-499a-987c-2266358f737c@googlegroups.com> |
| In reply to | #11756 |
I am still looking. There are 4 other successful queries executed before this one in the DataWindow init method. This is the only one with date type fields where the value is null. Could that be a factor? Richard
[toc] | [prev] | [next] | [standalone]
| From | D.J.W. van Kooten <vankooten@removethis.ic2.com> |
|---|---|
| Date | 2018-07-14 09:13 +0200 |
| Message-ID | <ik8jkdp1g1rq15busit9g7g3u5h9fqqro0@4ax.com> |
| In reply to | #11757 |
Replying on message of Fri, 13 Jul 2018 08:54:03 -0700 (PDT) from Pilks: Hello Richard, I am not familiair with VO2ADO but have you seen these links: http://www.vbforums.com/showthread.php?668857-Data-Provider-or-other-service-returned-an-E_FAIL-status https://stackoverflow.com/questions/10404315/why-am-i-getting-data-provider-or-other-service-returned-an-e-fail-status-sql-n Dick
[toc] | [prev] | [next] | [standalone]
| From | Pilks <richardp@lukhozi.co.za> |
|---|---|
| Date | 2018-07-16 08:13 -0700 |
| Message-ID | <26ea42c3-e1b5-46ed-8900-1bd0e9da0e5f@googlegroups.com> |
| In reply to | #11758 |
Dick Yes I did see them. I have tried to change both the sql_mode setting on the server and made sure they are date field types, not timestamps. Also the values that seem to cause a problem are null values, not invalid date values. I will keep at it though, thanks. Richard On Saturday, 14 July 2018 09:14:00 UTC+2, D.J.W. van Kooten wrote: > Replying on message of Fri, 13 Jul 2018 08:54:03 -0700 (PDT) from > Pilks: > > > Hello Richard, > > I am not familiair with VO2ADO but have you seen these links: > > http://www.vbforums.com/showthread.php?668857-Data-Provider-or-other-service-returned-an-E_FAIL-status > https://stackoverflow.com/questions/10404315/why-am-i-getting-data-provider-or-other-service-returned-an-e-fail-status-sql-n > > Dick
[toc] | [prev] | [next] | [standalone]
| From | gianluca.pinoli@proximacentauri.it |
|---|---|
| Date | 2018-07-16 03:19 -0700 |
| Message-ID | <e97cae23-cf9d-439e-963d-7e54d78f123e@googlegroups.com> |
| In reply to | #11757 |
Il giorno venerdì 13 luglio 2018 17:54:05 UTC+2, Pilks ha scritto: > I am still looking. There are 4 other successful queries executed before this one in the DataWindow init method. This is the only one with date type fields where the value is null. Could that be a factor? > > Richard Hi Richard, we had a similar problem upgrading from MySQL 5.1 to 5.5 It seem that MySQL consider dates prior to 1000-01-01 not valid, and from version 5.5 the default settings doesn't allow ZERO_DATE (0000-00-00). I think this could help even with MariaDB (isn't it a fork of MySQL 5.5?) You could try changing sql_mode on your server. https://dev.mysql.com/doc/refman/5.5/en/sql-mode.html Regards Gianluca
[toc] | [prev] | [next] | [standalone]
| From | Pilks <richardp@lukhozi.co.za> |
|---|---|
| Date | 2018-07-16 08:10 -0700 |
| Message-ID | <79368d2e-90e4-45f7-8f5e-24d14da8fb40@googlegroups.com> |
| In reply to | #11762 |
Gianluca Thanks for the suggestion, my sql_mode is already set correctly. Also the datetime fields are null (not zero or 0000-00-00). Not sure if that is affected by that setting? Richard On Monday, 16 July 2018 12:19:11 UTC+2, gianluc...@proximacentauri.it wrote: > Il giorno venerdì 13 luglio 2018 17:54:05 UTC+2, Pilks ha scritto: > > I am still looking. There are 4 other successful queries executed before this one in the DataWindow init method. This is the only one with date type fields where the value is null. Could that be a factor? > > > > Richard > > Hi Richard, > we had a similar problem upgrading from MySQL 5.1 to 5.5 > It seem that MySQL consider dates prior to 1000-01-01 not valid, and from version 5.5 the default settings doesn't allow ZERO_DATE (0000-00-00). > > I think this could help even with MariaDB (isn't it a fork of MySQL 5.5?) > You could try changing sql_mode on your server. > > https://dev.mysql.com/doc/refman/5.5/en/sql-mode.html > > Regards > Gianluca
[toc] | [prev] | [next] | [standalone]
| From | Sherlock <sherlock@sherlock.com.au> |
|---|---|
| Date | 2018-07-14 07:19 -0700 |
| Message-ID | <925682f1-1e76-4da1-a966-c2eb182fc793@googlegroups.com> |
| In reply to | #11756 |
ODBS with MySQL or Postgres seen to many weird issues with these drivers. Native support or nothing With MariaDB being a mySQL spin off does the "libmySQL.dll" work with DEVO MySQL classes.. Never tried. Phil
[toc] | [prev] | [next] | [standalone]
| From | "Wolfgang Riedmann" <wriedmann@gmail.com> |
|---|---|
| Date | 2018-07-15 07:38 +0200 |
| Message-ID | <fr04u0Fd99fU1@mid.individual.net> |
| In reply to | #11756 |
Hi Richard,
do you have the VO2Ado Pro version together with the sources?
If yes, try to look at the source code.
If not, buy the Pro upgrade and look at the code.
And try to debug the library to see what is going on.
Do you have the latest VO2Ado? Maybe this issue is already fixed.
Wolfgang
Pilks wrote:
> Hi All
>
> Maintaining and old system that uses VO 2.7 and makes use of VO2ADO
> to connect to a mysql database via ODBC. The server was upgraded to
> MariaDB recently and all was fine until we upgraded a workstation to
> Win 10. That person started experiencing problems with rounding of
> decimal numbers to integers when saving to the database. I updated
> the connector to a MariaDB connector and solved that problem.
>
> Now if I pull all fields from a table I get an error for the Win 10
> PC on the Execute method call:
>
> // Error message
> Error Code: Data provider or other service returned an E_FAIL status.
> Subsystem: Vo2Ado
> Error SubCode: 16389
>
> The code involved is in the init of a DataWindow:
> // sSqlText = "SELECT * FROM projects where project_id='2634'"
> SELF:oCmnd := AdoCommand{}
> SELF:oCmnd:ActiveConnection := oDMSC // global variable
> SELF:oCmnd:CommandText := sSqlText
> uRet := SELF:oCmnd:Execute(NIL,NIL,NIL) // Error on this line
>
> I am busy with a translation to XSharp but that is quite a long way
> off and this problem is immediate.
>
> Anyone with a clue? Maybe a description of the error subcode (16389)?
>
> TIA
>
> Richard
--
[toc] | [prev] | [next] | [standalone]
| From | Pilks <richardp@lukhozi.co.za> |
|---|---|
| Date | 2018-07-16 08:06 -0700 |
| Message-ID | <f4e5ba0b-34a2-4657-b876-4973cd71a6ad@googlegroups.com> |
| In reply to | #11760 |
Wolfgang
I unfortunately have an older free version (2.7.1.2730 for VO 2.7a), but thanks.
Richard
On Sunday, 15 July 2018 07:38:10 UTC+2, Wolfgang Riedmann wrote:
> Hi Richard,
>
> do you have the VO2Ado Pro version together with the sources?
>
> If yes, try to look at the source code.
> If not, buy the Pro upgrade and look at the code.
> And try to debug the library to see what is going on.
>
> Do you have the latest VO2Ado? Maybe this issue is already fixed.
>
> Wolfgang
>
>
> Pilks wrote:
>
> > Hi All
> >
> > Maintaining and old system that uses VO 2.7 and makes use of VO2ADO
> > to connect to a mysql database via ODBC. The server was upgraded to
> > MariaDB recently and all was fine until we upgraded a workstation to
> > Win 10. That person started experiencing problems with rounding of
> > decimal numbers to integers when saving to the database. I updated
> > the connector to a MariaDB connector and solved that problem.
> >
> > Now if I pull all fields from a table I get an error for the Win 10
> > PC on the Execute method call:
> >
> > // Error message
> > Error Code: Data provider or other service returned an E_FAIL status.
> > Subsystem: Vo2Ado
> > Error SubCode: 16389
> >
> > The code involved is in the init of a DataWindow:
> > // sSqlText = "SELECT * FROM projects where project_id='2634'"
> > SELF:oCmnd := AdoCommand{}
> > SELF:oCmnd:ActiveConnection := oDMSC // global variable
> > SELF:oCmnd:CommandText := sSqlText
> > uRet := SELF:oCmnd:Execute(NIL,NIL,NIL) // Error on this line
> >
> > I am busy with a translation to XSharp but that is quite a long way
> > off and this problem is immediate.
> >
> > Anyone with a clue? Maybe a description of the error subcode (16389)?
> >
> > TIA
> >
> > Richard
>
>
>
> --
[toc] | [prev] | [next] | [standalone]
| From | Pilks <richardp@lukhozi.co.za> |
|---|---|
| Date | 2018-07-19 08:54 -0700 |
| Message-ID | <0b3daf16-eeef-44e1-b034-44754994e3a8@googlegroups.com> |
| In reply to | #11756 |
Hi All
Just reporting back that I was able to find a workaround to the problem.
It turned out the date and datetime fields that allowed nulls gave problems. I had to change all occurrences where I selected all fields (select * from tablename where ...) from tables that had dates where they could be null. I also had to use DATE_FORMAT(dateField,'%Y-%m-%d') or similar to extract the date values in the select statement.
These two adjustments seemed to solve the problem for me.
Thanks for suggestions and assistance.
Richard
On Friday, 13 July 2018 17:45:28 UTC+2, Pilks wrote:
> Hi All
>
> Maintaining and old system that uses VO 2.7 and makes use of VO2ADO to connect to a mysql database via ODBC. The server was upgraded to MariaDB recently and all was fine until we upgraded a workstation to Win 10. That person started experiencing problems with rounding of decimal numbers to integers when saving to the database.
> I updated the connector to a MariaDB connector and solved that problem.
>
> Now if I pull all fields from a table I get an error for the Win 10 PC on the Execute method call:
>
> // Error message
> Error Code: Data provider or other service returned an E_FAIL status.
> Subsystem: Vo2Ado
> Error SubCode: 16389
>
> The code involved is in the init of a DataWindow:
> // sSqlText = "SELECT * FROM projects where project_id='2634'"
> SELF:oCmnd := AdoCommand{}
> SELF:oCmnd:ActiveConnection := oDMSC // global variable
> SELF:oCmnd:CommandText := sSqlText
> uRet := SELF:oCmnd:Execute(NIL,NIL,NIL) // Error on this line
>
> I am busy with a translation to XSharp but that is quite a long way off and this problem is immediate.
>
> Anyone with a clue? Maybe a description of the error subcode (16389)?
>
> TIA
>
> Richard
[toc] | [prev] | [next] | [standalone]
| From | epremuz@gmail.com |
|---|---|
| Date | 2018-10-30 13:42 -0700 |
| Message-ID | <295c8a02-b2e2-405e-99ef-b7f7fad77c4d@googlegroups.com> |
| In reply to | #11777 |
Richard, you are an ADO angel if such a thing even exists. Thank you.
In case someone googled this error and ended up here let me tell you that going the cheap way and disallowing nulls in your table won't help you, or at least it didn't help me. Also, this doesn't seem to be an issue with VO2ADO but more of a general ADO <--> MariaDB issue (or maybe even related to the ODBC driver, who knows).
For the record, this could be a regression between versions 2.0.15 and 2.0.18 of MariaDB ODBC's driver. Can't really test it as of now but might be useful information in case you need to troubleshoot this issue.
On Thursday, July 19, 2018 at 12:54:03 PM UTC-3, Pilks wrote:
> Hi All
>
> Just reporting back that I was able to find a workaround to the problem.
>
> It turned out the date and datetime fields that allowed nulls gave problems. I had to change all occurrences where I selected all fields (select * from tablename where ...) from tables that had dates where they could be null. I also had to use DATE_FORMAT(dateField,'%Y-%m-%d') or similar to extract the date values in the select statement.
>
> These two adjustments seemed to solve the problem for me.
>
> Thanks for suggestions and assistance.
>
> Richard
>
> On Friday, 13 July 2018 17:45:28 UTC+2, Pilks wrote:
> > Hi All
> >
> > Maintaining and old system that uses VO 2.7 and makes use of VO2ADO to connect to a mysql database via ODBC. The server was upgraded to MariaDB recently and all was fine until we upgraded a workstation to Win 10. That person started experiencing problems with rounding of decimal numbers to integers when saving to the database.
> > I updated the connector to a MariaDB connector and solved that problem.
> >
> > Now if I pull all fields from a table I get an error for the Win 10 PC on the Execute method call:
> >
> > // Error message
> > Error Code: Data provider or other service returned an E_FAIL status.
> > Subsystem: Vo2Ado
> > Error SubCode: 16389
> >
> > The code involved is in the init of a DataWindow:
> > // sSqlText = "SELECT * FROM projects where project_id='2634'"
> > SELF:oCmnd := AdoCommand{}
> > SELF:oCmnd:ActiveConnection := oDMSC // global variable
> > SELF:oCmnd:CommandText := sSqlText
> > uRet := SELF:oCmnd:Execute(NIL,NIL,NIL) // Error on this line
> >
> > I am busy with a translation to XSharp but that is quite a long way off and this problem is immediate.
> >
> > Anyone with a clue? Maybe a description of the error subcode (16389)?
> >
> > TIA
> >
> > Richard
[toc] | [prev] | [next] | [standalone]
| From | dlzc <dlzc1@cox.net> |
|---|---|
| Date | 2018-10-30 13:52 -0700 |
| Message-ID | <6ad8308f-b4cb-452f-a0d4-88df542627ae@googlegroups.com> |
| In reply to | #12094 |
Dear epr...: On Tuesday, October 30, 2018 at 1:42:35 PM UTC-7, epr...@gmail.com wrote: ... > For the record, this could be a regression between > versions 2.0.15 and 2.0.18 of MariaDB ODBC's driver. > Can't really test it as of now but might be useful > information in case you need to troubleshoot this > issue. Thanks for feeding "posterity"! It improves the quality of this resource. David A. Smith
[toc] | [prev] | [standalone]
Back to top | Article view | comp.lang.clipper.visual-objects
csiph-web