Thread: Re: [opendbx] MySQL unsupported data types
Brought to you by:
nose
Menu
▾
▴
libopendbx-devel
|
From: Norbert <no...@li...> - 2014-10-28 11:37:40
|
Hi Brad I don't know the Smalltalk implementation but OpenDBX still returns the value when you call opendbx_field_value() even if the exact type is unknown. For MySQL timestamps it's a string representation of an integer value. If you know that your column is a timestamp, you can use it as such in your application. Norbert Brad Selfridge <bss...@gm...> schrieb: >I am trying to convert an application to Smalltalk and the MySQL database is riddled with timestamp column types. However, OpenDbx returns an unsupported data type for time stamps. It is impossible to convert the column type to DateTime. Is there any possibility of adding timestamp as a supported type for Mysql? > >Brad Selfridge > >Sent from my iPad >------------------------------------------------------------------------------ >_______________________________________________ >libopendbx-devel mailing list >lib...@li... >https://lists.sourceforge.net/lists/listinfo/libopendbx-devel >http://www.linuxnetworks.de/doc/index.php/OpenDBX |
|
From: Brad <bss...@gm...> - 2014-10-28 12:53:40
|
I'm using an ORM framework. It tries to generate the appropriate object of the data value using the returned data type. No type, no object. My only option would be to tear into the framework and bypass/override a lot of code, thereby potentially nullifying the need of the framework. I guess I'm mystified why there are types not returned. Other tools show/return them? Please enlighten me. Brad Selfridge 913-269-2385 > On Oct 28, 2014, at 6:20 AM, Norbert <no...@li...> wrote: > > Hi Brad > > I don't know the Smalltalk implementation but OpenDBX still returns the value when you call opendbx_field_value() even if the exact type is unknown. > > For MySQL timestamps it's a string representation of an integer value. If you know that your column is a timestamp, you can use it as such in your application. > > > Norbert > > > Brad Selfridge <bss...@gm...> schrieb: > >> I am trying to convert an application to Smalltalk and the MySQL database is riddled with timestamp column types. However, OpenDbx returns an unsupported data type for time stamps. It is impossible to convert the column type to DateTime. Is there any possibility of adding timestamp as a supported type for Mysql? >> >> Brad Selfridge >> >> Sent from my iPad >> ------------------------------------------------------------------------------ >> _______________________________________________ >> libopendbx-devel mailing list >> lib...@li... >> https://lists.sourceforge.net/lists/listinfo/libopendbx-devel >> http://www.linuxnetworks.de/doc/index.php/OpenDBX > ------------------------------------------------------------------------------ > _______________________________________________ > libopendbx-devel mailing list > lib...@li... > https://lists.sourceforge.net/lists/listinfo/libopendbx-devel > http://www.linuxnetworks.de/doc/index.php/OpenDBX |
|
From: Norbert S. <no...@li...> - 2014-10-28 18:23:11
|
Hi Brad > I'm using an ORM framework. It tries to generate the appropriate > object of the data value using the returned data type. No type, > no object. My only option would be to tear into the framework and > bypass/override a lot of code, thereby potentially nullifying the > need of the framework. The best option might be if the ORM framework would provide all unknown data types as string or binary data. Then you would be at least able to access the data and transform it afterwards if necessary. Norbert |
|
From: Brad <bss...@gm...> - 2014-10-29 21:37:10
|
So, are you saying that OpenDBX does not/cannot always return the column types for tables? Brad Selfridge 913-269-2385 > On Oct 28, 2014, at 1:23 PM, Norbert Sendetzky <no...@li...> wrote: > > Hi Brad > >> I'm using an ORM framework. It tries to generate the appropriate >> object of the data value using the returned data type. No type, >> no object. My only option would be to tear into the framework and >> bypass/override a lot of code, thereby potentially nullifying the >> need of the framework. > > The best option might be if the ORM framework would provide all > unknown data types as string or binary data. Then you would be at > least able to access the data and transform it afterwards if necessary. > > > Norbert > > ------------------------------------------------------------------------------ > _______________________________________________ > libopendbx-devel mailing list > lib...@li... > https://lists.sourceforge.net/lists/listinfo/libopendbx-devel > http://www.linuxnetworks.de/doc/index.php/OpenDBX |
|
From: Brad S. <bss...@gm...> - 2014-10-31 02:52:19
|
I've researched the OpenDBX source files and have found that not all column types are being returned. It seems most databases supported have this anomaly. I'm curious as to why? It doesn't make sense to me why each database interface program wouldn't support all types for that database. I must not understand something. Please educate me. Thanks, Brad Selfridge > On Oct 28, 2014, at 1:23 PM, Norbert Sendetzky <no...@li...> wrote: > > Hi Brad > >> I'm using an ORM framework. It tries to generate the appropriate >> object of the data value using the returned data type. No type, >> no object. My only option would be to tear into the framework and >> bypass/override a lot of code, thereby potentially nullifying the >> need of the framework. > > The best option might be if the ORM framework would provide all > unknown data types as string or binary data. Then you would be at > least able to access the data and transform it afterwards if necessary. > > > Norbert > > ------------------------------------------------------------------------------ > _______________________________________________ > libopendbx-devel mailing list > lib...@li... > https://lists.sourceforge.net/lists/listinfo/libopendbx-devel > http://www.linuxnetworks.de/doc/index.php/OpenDBX |
|
From: Norbert S. <no...@li...> - 2014-10-31 07:07:22
|
Hi Brad > I've researched the OpenDBX source files and have found that not > all column types are being returned. It seems most databases > supported have this anomaly. I'm curious as to why? > > It doesn't make sense to me why each database interface program > wouldn't support all types for that database. I must not > understand something. Please educate me. OpenDBX supports the ANSI data types which have a defined format and semantics. Database vendors invented much more data types for special cases which doesn't fit into the ANSI scheme. These special data types are summarized as TYPE_UNKNOWN in OpenDBX which only means that they doesn't fit into the existing ANSI types and their data is returned in its native format without any conversion. So TYPE_UNKNOWN is only another data type for all remaining database specific types. Norbert |
|
From: Brad <bss...@gm...> - 2014-10-31 14:02:49
|
It is frustrating that there really is no such thing as ANSI standard SQL from virtually any of the database vendors. I understand your desire to provide some semblance of ANSI standard and I applaud you for your efforts. Would you be open to creating a new more inclusive "odbx_column_type_nonansi" function that does provide full support for each type? This way each user could choose to use either ANSI support or non-ANSI support for types. Brad Selfridge 913-269-2385 > On Oct 31, 2014, at 2:07 AM, Norbert Sendetzky <no...@li...> wrote: > > Hi Brad > >> I've researched the OpenDBX source files and have found that not >> all column types are being returned. It seems most databases >> supported have this anomaly. I'm curious as to why? >> >> It doesn't make sense to me why each database interface program >> wouldn't support all types for that database. I must not >> understand something. Please educate me. > > OpenDBX supports the ANSI data types which have a defined format and > semantics. Database vendors invented much more data types for special > cases which doesn't fit into the ANSI scheme. These special data types > are summarized as TYPE_UNKNOWN in OpenDBX which only means that they > doesn't fit into the existing ANSI types and their data is returned in > its native format without any conversion. So TYPE_UNKNOWN is only > another data type for all remaining database specific types. > > > Norbert > > > ------------------------------------------------------------------------------ > _______________________________________________ > libopendbx-devel mailing list > lib...@li... > https://lists.sourceforge.net/lists/listinfo/libopendbx-devel > http://www.linuxnetworks.de/doc/index.php/OpenDBX |
Thanks for helping keep SourceForge clean.
X