SqueakDBX August 2011

squeakdbx@lists.squeakfoundation.org

2 participants
7 discussions

Moving SqueakDBX mailing list to a new DBXTalk one
by Mariano Martinez Peck 22 Aug '11

22 Aug '11

Hi guys. We are moving the mailing list of squeakdbx(a)lists.squeakfoundation.org to a new google group: http://groups.google.com/group/dbxtalk We welcome you in the new mailing list and please deprecate as soon as possible the old one. Cheers -- Mariano http://marianopeck.wordpress.com

1 0

Re: [opendbx] [Pharo-users] DBXTypeNotSupoorted with Glorp
by Mariano Martinez Peck 16 Aug '11

16 Aug '11

On Tue, Aug 16, 2011 at 8:46 AM, Alain Rastoul <alr.dev(a)free.fr> wrote: > ** > Hi Mariano, > Yes, that is what is expected, but in the case of SQLite, the column type > changes to SQLITE_NULL for nulls and that is a problem in squeakdbx now. > I think column datatype should not be stored in the resultset in the case > of sqlite. > Other databases don't behave this way (as far as I can remember), so, > overriding moveNext for sqlite would probably be fine. > > So yes. Something is needed for Sqlite so that the column type and friends are fetched for every raw or at least when there is an unknown. At least there is a DBXSqlitePlatform that let you easily overwrite stuff ;) > Cheers > Alain > > "Mariano Martinez Peck" <marianopeck(a)gmail.com> a écrit dans le message de > news: CAA+-=mWHq6X9JGz-5qTyb3z5ZqdUwMwBV06B5AEZ=ivZVE4u4g(a)mail.gmail.com > ... > And here: http://www.linuxnetworks.de/doc/index.php/OpenDBX/C_API/Usage > > I can read: > > " Processing results > > After fetching a row, all values of this row are available for further > processing, as well as their name, length and type - but the name and the > type of a column won't change. Also the number of columns returned by > odbx_column_count<http://www.linuxnetworks.de/doc/index.php/OpenDBX/API/odbx_column_count>() > is fixed for the whole result. > > int i; > > for( i = 0; i < odbx_column_count( result ); i++ ) > { > fprintf( stdout, "Name: %s\n", odbx_column_name( result, i ) ); > fprintf( stdout, "Type: %d\n", odbx_column_type( result, i ) ); > fprintf( stdout, "Length: %d\n", odbx_field_length( result, i ) ); > fprintf( stdout, "Value: %s\n", odbx_field_value( result, i ) ); > } > > > Besides odbx_column_type<http://www.linuxnetworks.de/doc/index.php/OpenDBX/API/odbx_column_type>() > these functions don't return error codes. Instead, they return zero ( > odbx_field_length<http://www.linuxnetworks.de/doc/index.php/OpenDBX/API/odbx_field_length>()) > or NULL (odbx_column_name<http://www.linuxnetworks.de/doc/index.php/OpenDBX/API/odbx_column_name>() > and odbx_field_length<http://www.linuxnetworks.de/doc/index.php/OpenDBX/API/odbx_field_length>()), > but you shouldn't check for those because these values are also valid return > values. > > All numbers are returned as strings from the database regardless if they > are integers or floats. If you want to do arithmetic operations, you have to > convert them to their machine dependent binary representation first. > " > > On Mon, Aug 15, 2011 at 11:11 PM, Mariano Martinez Peck < > marianopeck(a)gmail.com> wrote: > >> >> >> On Mon, Aug 15, 2011 at 9:59 PM, Alain Rastoul <alr.dev(a)free.fr> wrote: >> >>> ** >>> Hi, >>> I finally found that when called in C with the same api calls that those >>> made by opendbx, sqlite correctly returns datatype of columns when fetching >>> rows, the problem is clearly that the data type is stored in SQueakDBX >>> column description for the resultset the first time it fetches the first >>> row. >>> For sqlite, squeakdbx should call the sqlite api to retrieve column >>> datatype for each row and each colum while fetching data. >>> >> >> Hi Alain. I am reading this: >> http://www.linuxnetworks.de/doc/index.php/OpenDBX/C_API/odbx_column_type >> >> From SqueakDBX, we send odbx_column_type ONCE PER RESULTSET. >> You can see this in #processNextResultSet:querySettings: that for every >> resultset it sends #processResultWithRows:resultHandle:querySettings: >> >> Now.... should we send odbx_column_type and friends ONCE PER RAW? As far >> as I can see, in other databases we don't need to do that. But maybe we are >> wrong and you are right. >> Norbert? >> >> Anyway, if you want to give it a try to Sqlite, what about overwrite >> #moveNext: in SqlitePlatform and do something to set the new type for every >> raw. >> >> From what I can see, if the type depends on each raw and it should be >> asked for every raw, then a design change is needed so that we can move the >> description from the REsultSet to the Raw :) >> >> >> But it may have implications I don't know. Perhaps squeakDbx could get >>> only true object values (are rawValues really needed) ?. >>> >> >> Well, it depends on the user needs. Now, a key point is what GLORP should >> use. >> >> >>> Or perhaps another solution would be to call the sqlite api if the >>> stored datatype is UNKNOWN in column description ... (only for sqlite, >>> but sounds like a bad trick) >>> >> >> sounds like a hask, but if it works it is at least a valid workaround. >> >> >>> I am perplexed ... >>> >>> Any idea is welcome >>> >>> Cheers >>> Alain >>> >>> "Mariano Martinez Peck" <marianopeck(a)gmail.com> a écrit dans le message >>> de news: >>> CAA+-=mW69g-MP3fQutJ9vVhAjRoP9eZdv5Z0Zkv9junYZeTyKw-JsoAwUIsXosN+BqQ9rBEUg(a)public.gmane.org >>> ... >>> >>> >>> On Sat, Aug 13, 2011 at 12:06 AM, Alain Rastoul <alr.dev(a)free.fr>wrote: >>> >>>> ** >>>> It doen't work. >>>> Howerver googling for opendbx msg00483, I found >>>> >>>> http://www.mail-archive.com/libopendbx-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ…<http://www.mail-archive.com/libopendbx-devel-5NWGOfrQmnetEtDZOKyKiw@public.…> >>>> >>> >>> yes, that one :) >>> >>> >>>> it seems to be the problem of the issue 10, and I think the same >>>> problem I have.. >>>> >>> >>> yes >>> Sorry, I cannot do more.... :( >>> >>> >>>> Strange that it doesn't work with MSSQL too.. >>>> >>>> >>>> "Mariano Martinez Peck" <marianopeck(a)gmail.com> a écrit dans le >>>> message de news: >>>> CAA+-=mW4rwrLMhMAzsLhQ5zEWZBG_Jg=BF2dKu3wsxw0=io=iQ(a)mail.gmail.com... >>>> >>>> >>>> On Fri, Aug 12, 2011 at 11:14 PM, Alain Rastoul <alr.dev(a)free.fr>wrote: >>>> >>>>> ** >>>>> I used the following script (about 2 months ago I think ) in Pharo 1.3 >>>>> "SqueakDBX" >>>>> Gofer new squeaksource: 'MetacelloRepository'; >>>>> package: 'ConfigurationOfSqueakDBX'; >>>>> load. >>>>> ConfigurationOfSqueakDBX project latestVersion load. >>>>> >>>>> "GLORP" >>>>> Gofer new squeaksource: 'MetacelloRepository'; >>>>> package: 'ConfigurationOfGlorpDBX'; >>>>> load. >>>>> ConfigurationOfGlorpDBX project latestVersion load. >>>>> >>>>> >>>> Yes, you are using SqueakDBX ;) you will move soon to DBXTalk :) >>>> >>>> >>>>> II use DBXTestCase for my test with the code I send in my email (is >>>>> it ok for you?), but I will have alook at DBXQueryTest too. >>>>> No problem to put it in the test suite - it makes me remember that I >>>>> still didn't send my license agreement to Stephane but I will do it >>>>> asap... I hate papers ;-) >>>>> >>>> >>>> in our case we don't need that ;) >>>> >>>> >>>>> >>>>> http://www.mail-archive.com/libopendbx-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ… >>>>> The link is broken >>>>> >>>> >>>> >>>> http://www.mail-archive.com/libopendbx-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ… >>>> >>>> this one works? >>>> >>>> >>>> -- >>>> Mariano >>>> http://marianopeck.wordpress.com >>>> >>>> >>> >>> >>> -- >>> Mariano >>> http://marianopeck.wordpress.com >>> >>> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > > ------------------------------ > > > ------------------------------------------------------------------------------ > uberSVN's rich system and user administration capabilities and model > configuration take the hassle out of deploying and managing Subversion and > the tools developers use with it. Learn more about uberSVN and get a free > download at: http://p.sf.net/sfu/wandisco-dev2dev > > ------------------------------ > > > > ------------------------------------------------------------------------------ > uberSVN's rich system and user administration capabilities and model > configuration take the hassle out of deploying and managing Subversion and > the tools developers use with it. Learn more about uberSVN and get a free > download at: http://p.sf.net/sfu/wandisco-dev2dev > > _______________________________________________ > libopendbx-devel mailing list > libopendbx-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/libopendbx-devel > http://www.linuxnetworks.de/doc/index.php/OpenDBX > > -- Mariano http://marianopeck.wordpress.com

1 0

Re: [Pharo-users] DBXTypeNotSupoorted with Glorp
by Mariano Martinez Peck 15 Aug '11

15 Aug '11

On Mon, Aug 15, 2011 at 9:59 PM, Alain Rastoul <alr.dev(a)free.fr> wrote: > ** > Hi, > I finally found that when called in C with the same api calls that those > made by opendbx, sqlite correctly returns datatype of columns when fetching > rows, the problem is clearly that the data type is stored in SQueakDBX > column description for the resultset the first time it fetches the first > row. > For sqlite, squeakdbx should call the sqlite api to retrieve column > datatype for each row and each colum while fetching data. > Hi Alain. I am reading this: http://www.linuxnetworks.de/doc/index.php/OpenDBX/C_API/odbx_column_type >From SqueakDBX, we send odbx_column_type ONCE PER RESULTSET. You can see this in #processNextResultSet:querySettings: that for every resultset it sends #processResultWithRows:resultHandle:querySettings: Now.... should we send odbx_column_type and friends ONCE PER RAW? As far as I can see, in other databases we don't need to do that. But maybe we are wrong and you are right. Norbert? Anyway, if you want to give it a try to Sqlite, what about overwrite #moveNext: in SqlitePlatform and do something to set the new type for every raw. >From what I can see, if the type depends on each raw and it should be asked for every raw, then a design change is needed so that we can move the description from the REsultSet to the Raw :) But it may have implications I don't know. Perhaps squeakDbx could get only > true object values (are rawValues really needed) ?. > Well, it depends on the user needs. Now, a key point is what GLORP should use. > Or perhaps another solution would be to call the sqlite api if the stored > datatype is UNKNOWN in column description ... (only for sqlite, but sounds > like a bad trick) > sounds like a hask, but if it works it is at least a valid workaround. > I am perplexed ... > > Any idea is welcome > > Cheers > Alain > > "Mariano Martinez Peck" <marianopeck(a)gmail.com> a écrit dans le message de > news: CAA+-=mW69g-MP3fQutJ9vVhAjRoP9eZdv5Z0Zkv9junYZeTyKw(a)mail.gmail.com > ... > > > On Sat, Aug 13, 2011 at 12:06 AM, Alain Rastoul <alr.dev(a)free.fr> wrote: > >> ** >> It doen't work. >> Howerver googling for opendbx msg00483, I found >> >> http://www.mail-archive.com/libopendbx-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ…<http://www.mail-archive.com/libopendbx-devel-5NWGOfrQmnetEtDZOKyKiw@public.…> >> > > yes, that one :) > > >> it seems to be the problem of the issue 10, and I think the same problem >> I have.. >> > > yes > Sorry, I cannot do more.... :( > > >> Strange that it doesn't work with MSSQL too.. >> >> >> "Mariano Martinez Peck" <marianopeck(a)gmail.com> a écrit dans le message >> de news: >> CAA+-=mW4rwrLMhMAzsLhQ5zEWZBG_Jg=BF2dKu3wsxw0=io=iQ(a)mail.gmail.com... >> >> >> On Fri, Aug 12, 2011 at 11:14 PM, Alain Rastoul <alr.dev(a)free.fr> wrote: >> >>> ** >>> I used the following script (about 2 months ago I think ) in Pharo 1.3 >>> "SqueakDBX" >>> Gofer new squeaksource: 'MetacelloRepository'; >>> package: 'ConfigurationOfSqueakDBX'; >>> load. >>> ConfigurationOfSqueakDBX project latestVersion load. >>> >>> "GLORP" >>> Gofer new squeaksource: 'MetacelloRepository'; >>> package: 'ConfigurationOfGlorpDBX'; >>> load. >>> ConfigurationOfGlorpDBX project latestVersion load. >>> >>> >> Yes, you are using SqueakDBX ;) you will move soon to DBXTalk :) >> >> >>> II use DBXTestCase for my test with the code I send in my email (is it >>> ok for you?), but I will have alook at DBXQueryTest too. >>> No problem to put it in the test suite - it makes me remember that I >>> still didn't send my license agreement to Stephane but I will do it >>> asap... I hate papers ;-) >>> >> >> in our case we don't need that ;) >> >> >>> >>> http://www.mail-archive.com/libopendbx-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ… >>> The link is broken >>> >> >> >> http://www.mail-archive.com/libopendbx-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ… >> >> this one works? >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > > -- Mariano http://marianopeck.wordpress.com

1 1

Re: [Pharo-users] DBXTypeNotSupoorted with Glorp
by Mariano Martinez Peck 12 Aug '11

12 Aug '11

On Fri, Aug 12, 2011 at 9:39 PM, Alain Rastoul <alr.dev(a)free.fr> wrote: > ** > hi Guillermo, > > you are right, I didn't use rawValues , and that was the problem. > The problem is not with Glorp but with opendbx and in fact it is the same > as the issue pointed to by Mariano (issue 10) and another (issue 16) > I have a simpler test to reproduce than yours (in fact you don't need to > use UNION in your test): > Hi Alain. First of all, thanks for poiting out the bug. Now, Guille asked you how did you install SqueakDBX/GlorpDBX because we are VERY near to release a new version of the new project called DBXTalk in which we will release a new version of SqueakDBX, which will be called OpenDBXDriver and a new release of GlorpDBX and Glorp, which we port the latest version from VW. You will have more news very soon, but I recommend you to migrate to this new stuff once it is out. > > | settings dbc stmt resultSet coll | > settings := DBXConnectionSettings > host: SmalltalkImage current imagePath, '/' > port: '' > database: 'testdb.dat' > userName: '' > userPassword: ''. > dbc := DBXConnection platform: DBXSqlitePlatform new settings: settings. > [ > dbc connect. > dbc open. > dbc execute: 'drop table if exists foo'. > dbc execute: 'create table foo (id int not null, name varchar(64) null )'. > dbc execute: 'insert into foo values(1, null )'. > dbc execute: 'insert into foo values(2, ''riptobe'' )'. > resultSet := dbc execute: 'SELECT * FROM foo'. > coll := OrderedCollection new. > "error here for null value in second row" > resultSet rows do: [ :r | coll add: r values ]. > coll inspect. > ] ensure: [ dbc close ]. > > I am out of time right now, but I would love if you or someone can take this piece of code and "adapt it" as a regular SqueakDBX test. If you do this, please do it directly in the package OpenDBXDriverTests of the repo http://www.squeaksource.com/DBXTalk. We really welcome your test :) You can add it to: DBXQueryTest. Take a look at to the existing tests there. > The problem is that opendbx doesn't return the correct datatype for > columns when they have null values, apparently it keeps the description for > the column that was readen for the first row (?) > Can you confirm it is this problem? http://www.mail-archive.com/libopendbx-devel@lists.sourceforge.net/msg00483… If it is...then it seems there is no fix :( > And the same problem exists with MSSQL, it is not related to the special > sqlite UNKNOW datatype but a problem in opendbx (my test also breaks with > mssql) > I am writing a test case for that, > excellent. > and I will also have a look at opendbx source code. > > great. Don't be shy to ask to ask and OpenDBX mailing list. > Cheers > Alain > > "Guillermo Polito" <guillermopolito(a)gmail.com> a écrit dans le message de > news: CAOBmb52JNRM+xQBx9kqNm9aMero3avyriXWsytbMqK=JBH8KAg(a)mail.gmail.com > ... > Hi Alain! > > where did you get GlorpDBX? :) Was it from the DBXTalk repo? > > > On Thu, Aug 11, 2011 at 5:28 PM, Alain Rastoul < > alr.dev-GANU6spQydw(a)public.gmane.org <alr.dev(a)free.fr>> wrote: > >> ** >> Hi Mariano >> >> I may be wrong, but I don't think that this issue is not related, I have >> first checked that reading my data with squeakdbx is ok. >> > > How did you read the data? Using values or raw values? > > Can you send us/me the query sent by glorp? Is it a polymorphic or > inheritance query? > > > Thanks! > Guille > >> >> After searching a bit I think that the problem is in Glorp in >> >> DBXPlatform>>createDataTypesMap >> "Creates and returns a map that maps Smalltalk classes to SQL datatypes. >> The 16r means it is hexadecimal." >> ^Dictionary new >> ... >> at: 16rFF put: (DBXTypeNotSupported type: #UNKNOWN); >> Perhaps a solution would be I think it should be something like >> at: 16rFF put: (DBXTypeNotSupported type: UndefinedObject); >> with a fromDbxString method defined in UndefinedObject. >> fromDbxString: aString >> ^ convert the string to the true column datatype >> >> The problem here is that there should be a conversion from the string to >> the column datatype and the column datatype is unknown here... >> I don't know either if it is possible to get it from squeakdbx at this >> point (while fetching data) ? >> >> >> >> "Mariano Martinez Peck" <marianopeck(a)gmail.com> a écrit dans le message >> de >> news:CAA+-=mWQ8y4zLdQbhDx3-hBPXUF_-S9wtvVOD8ia+=6tC8-ufg@mail.gmail.com<news:CAA+-=mWQ8y4zLdQbhDx3-hBPXUF_-S9wtvVOD8ia+=6tC8-ufg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> >> ... >> >> >> On Thu, Aug 11, 2011 at 10:02 PM, Alain Rastoul <alr.dev(a)free.fr> wrote: >> >>> Hi >>> >>> I 'm writing a small app with pharo +seaside + glorp + squeakdbx + sqlite >>> and I have a problem reading null values from my database. >>> >> >> Hi Alain. Do you know exactly which query is being sent? Do you think it >> can be related to this: >> http://code.google.com/p/dbxtalk/issues/detail?id=10 ? >> >> >> >>> It seems that glorp stores a DbxTypeNotSupported in the column >>> description for null values when the first row has a null value (the column >>> datatype is varchar). >>> Any workaround or advice is welcome before I dig into Glorp code >>> TIA >>> >>> Alain >>> >>> >>> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> >> > -- Mariano http://marianopeck.wordpress.com

1 0

Re: DBXTalk logo
by Mariano Martinez Peck 12 Aug '11

12 Aug '11

Hi Natasha. Thanks for this offer :) I have no idea yet what I want (as always!) but I can talk to the team to see if we get some idea. The project itself is about relational databases. JB can probably help you to understand ;) DBXTalk is a suite of tools for connecting to databases from Smalltalk. Apart from having a "driver" which connects Smalltalk to databases, it provides some tools. For example, a tool to automatize the work needed for an application to persist into a database. The website of the project is in here: http://www.squeakdbx.org/ Notice that the project was previously named SqueakDBX and now it is DBXTalk. The idea is that we will create a new website for DBXTalk :) The DBX is because DB is DataBase and when you use the X you usually mean "any". So it is kind of saying that we can work with *any* database. In addition, the "talk" is to relate it to Smalltalk ;) I will ask the team to see if they have an idea for the logo! Thanks a lot in advance. On Fri, Aug 12, 2011 at 1:55 PM, Natacha PERRIN <p.natach(a)gmail.com> wrote: > Hi ! > Thank you for thinking of me for your logo. > I can try to make it to the end of August if you want. Tell me more > about the software. You already have an idea of what you want? > It is necessary that I get to re-install photoshop on my computer and I > begin. > > -- Mariano http://marianopeck.wordpress.com

2 2

Re: [Pharo-users] DBXTypeNotSupoorted with Glorp
by Mariano Martinez Peck 11 Aug '11

11 Aug '11

On Thu, Aug 11, 2011 at 10:02 PM, Alain Rastoul <alr.dev(a)free.fr> wrote: > Hi > > I 'm writing a small app with pharo +seaside + glorp + squeakdbx + sqlite > and I have a problem reading null values from my database. > Hi Alain. Do you know exactly which query is being sent? Do you think it can be related to this: http://code.google.com/p/dbxtalk/issues/detail?id=10 ? > It seems that glorp stores a DbxTypeNotSupported in the column description > for null values when the first row has a null value (the column datatype is > varchar). > Any workaround or advice is welcome before I dig into Glorp code > TIA > > Alain > > > -- Mariano http://marianopeck.wordpress.com

1 0

Changing the mailing list
by Mariano Martinez Peck 05 Aug '11

05 Aug '11

Hi guys. As you know, we are renaming the project to DBXTalk, we are developing some new tools, and we have new support of ESUG and a new team working on these projects. As part of the changes, we also want to rename the url of the website and the name of the mailing-list. We don't want to be coupled neither with Squeak or Pharo. We have created an issue tracker in Google Code. So, the question is, do you mind if we move this mailman mailing list to a google group? Thanks -- Mariano http://marianopeck.wordpress.com

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

SqueakDBX August 2011