August 2011 - Pharo-users - lists.pharo.org

ESUG = Edinburgh Airport

by Benjamin

Is there some of you who will arrive at the Edinburgh airport around 17h ? Because Jannik Laval and I will be there, so if we can share a taxi and be a bit less lost, it could be cool :) Ben

Aug. 20, 2011

Re: [Pharo-users] Memories about an ESUG talk: Smalltalk's Image Problem

by Sean P. DeNigris

Offray wrote: > > If Smalltalk is so good, why is not widely known ? > The real answer: It's an invalid question because it presupposes the invalid assumption that quality -> wide acceptance. Of course, there are an infinite number of concrete "reasons", but ultimately it's that "human progress" that happens in a straight line over time is an illusion. We are not immune to the chaos of the universe. Ideas (as systems interacting with all the systems of their environment, and the environments of those environments...) do not take off, or not, based on quality, but on the sum of the forces acting on them, which are mostly beyond our understanding or control. What you could actually say that they will hear: see below Offray wrote: > > Which famous/big project is made with Smalltalk ? > Mariano nailed it: Smalltalk is considered such a competitive advantage that companies that use it usually won't admit it, and often won't allow the vendors to talk about it. -- View this message in context: http://forum.world.st/Memories-about-an-ESUG-talk-Smalltalk-s-Image-Problem… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 19, 2011

Re: [Pharo-users] Memories about an ESUG talk: Smalltalk's Image Problem

by Mariano Martinez Peck

On Fri, Aug 19, 2011 at 8:16 PM, Offray Vladimir Luna CÃ¡rdenas < offray(a)riseup.net> wrote: > HI all, > > I was making a talk here in Colombia trying to invite people to conform a > Smalltalk study group. I was showing them Pier and Seaside as "selling > points" for making a project and there is some initial interest. The typical > questions about: > > * If Smalltalk is so good, why is not widely known ? > Half serious / half jookes - Marketing - It was expensive -> none (or few?) open-source dialect existed when Java arrived. - Something that is easy and simple is difficult to sell. Companies are stupid. They buy complexity. - Because doing Smalltalk is a letal weapon for a company. Imagine you have a super secret tool that makes a big difference with your competirors, would you tell it to your competiros? - Smalltalkers used to be quite close people and nobody likes to document -> Smalltalk has few documentation in comparison to other languages. - Smalltalk is too different from all the rest of the languages. - Companies are afraid of using Smalltalk because nobody use it -> endess loop. - Because few universities teach Smalltalk now. - Because it is difficult to find Smalltalkers, hence companies don't want to buy a proyect where they cannot find people to maintain it after. * Which famous/big project is made with Smalltalk ? > - JP Morgan - Telecom - AMD - Banks - Medical stuff - Military http://www.goodstart.com/who-uses-smalltalk.ssp http://www.esug.org/wiki/pier/Smaltalk/Companies > where in place. I think that Pier, Seaside, Etoys, Scratch, DrGeo, Croquet, > - Moose, Magma, Gemstone > are really good projects to motivate people towards learning Smmalltalk, > but they're kind of "niche" projects (I have no problem with that), but > searching for information about who to solve these questions I found this > talk on ESUG 2009: > > http://www.esug.org/**Conferences/2009/Current+List+** > of+Talks/Smalltalk%27s+Image+**Problem<http://www.esug.org/Conferences/2009/Current+List+of+Talks/Smalltalk%27s+Im…> > > So I wonder if anyone has the memories/slides of this talk and, of course, > what community thinks about these questions. > > Thanks, > > Offray > > -- Mariano http://marianopeck.wordpress.com

Aug. 19, 2011

Memories about an ESUG talk: Smalltalk's Image Problem

by Offray Vladimir Luna CÃ¡rdenas

HI all, I was making a talk here in Colombia trying to invite people to conform a Smalltalk study group. I was showing them Pier and Seaside as "selling points" for making a project and there is some initial interest. The typical questions about: * If Smalltalk is so good, why is not widely known ? * Which famous/big project is made with Smalltalk ? where in place. I think that Pier, Seaside, Etoys, Scratch, DrGeo, Croquet, are really good projects to motivate people towards learning Smmalltalk, but they're kind of "niche" projects (I have no problem with that), but searching for information about who to solve these questions I found this talk on ESUG 2009: http://www.esug.org/Conferences/2009/Current+List+of+Talks/Smalltalk%27s+Im… So I wonder if anyone has the memories/slides of this talk and, of course, what community thinks about these questions. Thanks, Offray

Aug. 19, 2011

Fwd: [ANN] Fuel release version 1.6

by Mariano Martinez Peck

---------- Forwarded message ---------- From: Martin Dias <tinchodias(a)gmail.com> Date: Fri, Aug 19, 2011 at 6:14 AM Subject: [ANN] Fuel release version 1.6 To: esug-list(a)lists.esug.org, pharo-project(a)lists.gforge.inria.fr Cc: Mariano Martinez Peck <marianopeck(a)gmail.com> Hello! I want to announce the new release version number 1.6 of Fuel, a binary serialization framework for Pharo that provides extremely fast deserialization. More information on our home page<http://rmod.lille.inria.fr/web/pier/software/Fuel>. Again, I thank ESUG for sponsoring me through the SummerTalk<http://www.esug.org/wiki/pier/Promotion/SummerTalk/SummerTalk2011>program. You can download this version in Pharo 1.2.1 with: Gofer new squeaksource: 'Fuel'; package: 'ConfigurationOfFuel'; load. ((Smalltalk at: #ConfigurationOfFuel) project version: '1.6') load. This version does not add any new concrete functionality but has two main achievements: a performance improvement and a design clean up. Many changes included in this release are part of a design clean up. They are a necessary step forward to new functionalities that are coming soon. They make code more understandable. They enable simpler extension. Happily they also helped to improve serialization performance by reducing unnecessary interactions. And it is specially important a bottleneck in graph analysis stage we have successfully attacked, obtaining great results. Details: - Removed explicit references to cluster classes scattered around the system. For example, in previous versions Float>>fuelCluster has an explicit reference to FLFloatCluster. This version replaces this by a double dispatch interaction. - Clusters: Better reification. Removed annoying IDs. Removed Singleton instance creation mechanism, now mappers manage uniqueness in a better way. - Mappers: They were simplified. New mapping machanism inspired on Chain of Responsibility pattern. The global objects detection has been optimized considerably. - Analyzer: Part of its behavior and state has been moved to a new abstraction called 'clusterization'. Best regards, MartÃn Dias -- Mariano http://marianopeck.wordpress.com

Aug. 19, 2011

Re: [Pharo-users] [opendbx] DBXTypeNotSupoorted with Glorp

by Alain Rastoul

Hi Mariano, here is a small test to reproduce the problem. Cheers, Alain "Mariano Martinez Peck" <marianopeck(a)gmail.com> a Ã©crit dans le message de news: CAA+-=mUQtO+BRB3zWxcM904M_acNcAbjHNyXCjyGx4=+6f02GA(a)mail.gmail.com... 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-JsoAwUIsXosN+BqQ9rBEUg(a)public.gmane.org... 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() 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() these functions don't return error codes. Instead, they return zero (odbx_field_length()) or NULL (odbx_column_name() and 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… 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

Aug. 16, 2011

Re: [Pharo-users] [opendbx] DBXTypeNotSupoorted with Glorp

by Mariano Martinez Peck

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

Aug. 16, 2011

Re: [Pharo-users] DBXTypeNotSupoorted with Glorp

by Mariano Martinez Peck

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(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 > > -- Mariano http://marianopeck.wordpress.com

Aug. 15, 2011

Re: [Pharo-users] DBXTypeNotSupoorted with Glorp

by Mariano Martinez Peck

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

Aug. 15, 2011

Re: [Pharo-users] DBXTypeNotSupoorted with Glorp

by Alain Rastoul

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. But it may have implications I don't know. Perhaps squeakDbx could get only true object values (are rawValues really needed) ?. 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) 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… 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-JsoAwUIsXosN+BqQ9rBEUg(a)public.gmane.org... 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

Aug. 15, 2011