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

Re: [Pharo-users] Best Practices for Bundling Documentation

by Stephane Ducasse

Hello evan Cool I want to read them! If you have your code in github you can include pillar files there and with travis build the pdf as I did for the booklets. I prefer to separate tutorials from code. I would go for MyStuff MyStuffTutorial or This way readers can get the pdf https://github.com/SquareBracketAssociates/Booklet-BuildingMemoryGameWithBl… or https://github.com/SquareBracketAssociates/Booklet-Mocking I can help you to set it up. After you booklet can be published on the Pharo books page too. stef On Sun, Aug 6, 2017 at 1:34 AM, Evan Donahue <emdonahu(a)gmail.com> wrote: > Hello, > > The projects are a logic programming and machine learning system > respectively, so they probably warrant more involved tutorial-style > documentation. I will take a look at the Pillar docs, but just to think > ahead a bit, assuming I write up some docs in Pillar, what would be the best > way to distribute those? Can they be packaged with the code or would the > docs be outside the image? If outside, where do people tend to host them? > > Thanks, > Evan > > > > -- > View this message in context: http://forum.world.st/Best-Practices-for-Bundling-Documentation-tp4958788p4… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

Aug. 6, 2017

Re: [Pharo-users] Glorp: `session login` fails for Garage SQLite

by Pierce Ng

On Sun, Aug 06, 2017 at 12:54:41AM +0200, Herby VojÄÃk wrote: > Pharo is 6.1, Glorp, Garage etc. are #stable loaded from Pharo60 > catalog (see attachment). You may want to try GlorpSQLite. Load from Catalog Browser into a fresh 60510 image. All 889 tests should pass, as has been the case since Pharo 5. In GlorpSQLite, #encoding is implemented by UDBCDatabaseDriver. Pierce

Aug. 6, 2017

Re: [Pharo-users] Glorp: `session login` fails for Garage SQLite

by Guillermo Polito

How did you install garage and glorp? Catalog, configurations? Can you paste here the installation instructions you followed? On Sun, Aug 6, 2017 at 1:37 AM, Herby VojÄÃk <herby(a)mailbox.sk> wrote: > Herby VojÄÃk wrote: > >> Guillermo Polito wrote: >> >>> AFAIR, PharoDatabaseAccessor was meant to work with SqueakDBX/DBXTalk >>> driver. No other driver should use it. At the time Garage did not even >>> exist. >>> >>> So I'd say that you should not use PharoDatabaseAccessor with another >>> driver than the one it was originally mean to? I do not know exactly >>> your setup, I was not following this thread. >>> >>> Really I cannot tell much more. This was really long time ago. >>> >> >> Great to know! >> >> I am not using it consciously, though. System somehow selects it and >> uses it in the background (I just do MyDescriptorSystem sessionForLogin: >> myLoginObject; and before that I set GarageGlorpDrive to be the default). >> >> This seems to be the actual fix (make Glorp with Garage not use >> PharoDatabaseAccessor). >> > > Actually, probably not. It is more in, it should be fixed to work with > Garage. It has lots of functionality there... :-( > > > >> Herby >> >> >>> On Sun, Aug 6, 2017 at 12:20 AM, Herby VojÄÃk <herby(a)mailbox.sk >>> <mailto:herby@mailbox.sk>> wrote: >>> >>> Esteban A. Maringolo wrote: >>> >>> Herby, >>> >>> I regularly use `session login`, but I don't use SQLite in >>> Pharo, but I >>> do in VisualWorks and it works just fine. >>> Maybe if there is a bug we should fix it. Even with a no-op method. >>> >>> Regards! >>> >>> Esteban A. Maringolo >>> >>> >>> It's hard. The problem is >>> >>> PharoDatabaseAccessor >> encoding >>> ^self connection queryEncoding >>> >>> which overrides parent, which is atm: >>> >>> encoding >>> "The connection is specific to the dialect; some dialects will need >>> to override this method." >>> >>> ^connection encoding >>> >>> The former was added at GuillermoPolito.73 back in 2011 (and the >>> latter was the same back then). It probably fixed something, but I >>> don't see any implementors of queryEncoding atm (definitely not in >>> Garage). From the diff it is clear lots of databases and drivers >>> have gone. Now, why was it change for Pharo (and does it need to be >>> changed in 2017)? >>> >>> Ccing Guillermo Polito. >>> >>> Herby >>> >>> P.S.: I wonder how it is that no one actually had problem with this? >>> This predictably fails on `session login` on pharo, unless >>> queryEncoding is somehow magically present without seeing it in >>> source code for other platforms? >>> >>> >>> 2017-08-05 15:52 GMT-03:00 Herby VojÄÃk <herby(a)mailbox.sk >>> <mailto:herby@mailbox.sk> >>> <mailto:herby@mailbox.sk <mailto:herby@mailbox.sk>>>: >>> >>> Alistair Grant wrote: >>> >>> Hi Herby, >>> >>> On 5 August 2017 at 18:09, Herby >>> VojÄÃk<herby(a)mailbox.sk <mailto:herby@mailbox.sk> >>> <mailto:herby@mailbox.sk <mailto:herby@mailbox.sk>>> wrote: >>> >>> Hello! >>> >>> First of all, what is preferred way to (first time) >>> login >>> into database? I >>> had the impression that `aDatabaseAccessor login` >>> is sorta >>> low-level, and >>> one should do `session login` (after all, it is >>> session you >>> get to work >>> with, not an accessor). >>> >>> But with Garage SQLite, `session login`, when >>> accessor is >>> not logged, always >>> fails with "MessageNotUnderstood: >>> GASqlite3Driver>>queryEncoding". >>> >>> Should one not use `session login` at all, then (when >>> accessor is logged, it >>> just does nothing, if it isn't, it connects the >>> accessor, >>> but tries to do >>> some additional work which always fails)? >>> >>> Herby >>> >>> >>> From memory this is caused by differences between >>> VisualWorks >>> and Pharo. >>> >>> Anyway, it is discussed and resolved in: >>> >>> http://forum.world.st/Glorp-SQLite3-issue-td4899792.html >>> <http://forum.world.st/Glorp-SQLite3-issue-td4899792.html> >>> <http://forum.world.st/Glorp-SQLite3-issue-td4899792.html >>> <http://forum.world.st/Glorp-SQLite3-issue-td4899792.html>> >>> >>> >>> Doesn't look like solved to me. Anyway, at least I know it >>> is known >>> for year and no-one seemed to see it as a bug. >>> >>> I think it is one (you cannot just send queryEncoding where >>> no class >>> implements it and be fine, imo). >>> >>> So what is the state of `session login`? Is it meant to be >>> used, or >>> everyone just took a step down to low-level and uses `accessor >>> login` instead? :-( >>> >>> >>> Cheers, >>> Alistair >>> >>> >>> Thanks, Herby >>> >>> >>> >>> >>> >>> >>> -- >>> >>> >>> >>> Guille Polito >>> >>> >>> Research Engineer >>> >>> French National Center for Scientific Research - _http://www.cnrs.fr_ >>> >>> >>> >>> *Web:* _http://guillep.github.io_ >>> >>> *Phone: *+33 06 52 70 66 13 >>> >>> >> >> > -- Guille Polito Research Engineer French National Center for Scientific Research - *http://www.cnrs.fr* <http://www.cnrs.fr> *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Aug. 6, 2017

Re: [Pharo-users] PetitParser: Parse X as long as it's not Y

by Sean P. DeNigris

vonbecmann wrote > did you try with negate? That is the standard trick with PP, but the problem here is that I'm trying to say, not just "anything which is not Y", but "any string of these characters as long is it doesn't also match Y" ----- Cheers, Sean -- View this message in context: http://forum.world.st/PetitParser-Parse-X-as-long-as-it-s-not-Y-tp4958895p4… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 6, 2017

Re: [Pharo-users] Glorp: `session login` fails for Garage SQLite

by Herby VojÄÃk

Herby VojÄÃk wrote: > Guillermo Polito wrote: >> AFAIR, PharoDatabaseAccessor was meant to work with SqueakDBX/DBXTalk >> driver. No other driver should use it. At the time Garage did not even >> exist. >> >> So I'd say that you should not use PharoDatabaseAccessor with another >> driver than the one it was originally mean to? I do not know exactly >> your setup, I was not following this thread. >> >> Really I cannot tell much more. This was really long time ago. > > Great to know! > > I am not using it consciously, though. System somehow selects it and > uses it in the background (I just do MyDescriptorSystem sessionForLogin: > myLoginObject; and before that I set GarageGlorpDrive to be the default). > > This seems to be the actual fix (make Glorp with Garage not use > PharoDatabaseAccessor). Actually, probably not. It is more in, it should be fixed to work with Garage. It has lots of functionality there... :-( > > Herby > >> >> On Sun, Aug 6, 2017 at 12:20 AM, Herby VojÄÃk <herby(a)mailbox.sk >> <mailto:herby@mailbox.sk>> wrote: >> >> Esteban A. Maringolo wrote: >> >> Herby, >> >> I regularly use `session login`, but I don't use SQLite in >> Pharo, but I >> do in VisualWorks and it works just fine. >> Maybe if there is a bug we should fix it. Even with a no-op method. >> >> Regards! >> >> Esteban A. Maringolo >> >> >> It's hard. The problem is >> >> PharoDatabaseAccessor >> encoding >> ^self connection queryEncoding >> >> which overrides parent, which is atm: >> >> encoding >> "The connection is specific to the dialect; some dialects will need >> to override this method." >> >> ^connection encoding >> >> The former was added at GuillermoPolito.73 back in 2011 (and the >> latter was the same back then). It probably fixed something, but I >> don't see any implementors of queryEncoding atm (definitely not in >> Garage). From the diff it is clear lots of databases and drivers >> have gone. Now, why was it change for Pharo (and does it need to be >> changed in 2017)? >> >> Ccing Guillermo Polito. >> >> Herby >> >> P.S.: I wonder how it is that no one actually had problem with this? >> This predictably fails on `session login` on pharo, unless >> queryEncoding is somehow magically present without seeing it in >> source code for other platforms? >> >> >> 2017-08-05 15:52 GMT-03:00 Herby VojÄÃk <herby(a)mailbox.sk >> <mailto:herby@mailbox.sk> >> <mailto:herby@mailbox.sk <mailto:herby@mailbox.sk>>>: >> >> Alistair Grant wrote: >> >> Hi Herby, >> >> On 5 August 2017 at 18:09, Herby >> VojÄÃk<herby(a)mailbox.sk <mailto:herby@mailbox.sk> >> <mailto:herby@mailbox.sk <mailto:herby@mailbox.sk>>> wrote: >> >> Hello! >> >> First of all, what is preferred way to (first time) >> login >> into database? I >> had the impression that `aDatabaseAccessor login` >> is sorta >> low-level, and >> one should do `session login` (after all, it is >> session you >> get to work >> with, not an accessor). >> >> But with Garage SQLite, `session login`, when >> accessor is >> not logged, always >> fails with "MessageNotUnderstood: >> GASqlite3Driver>>queryEncoding". >> >> Should one not use `session login` at all, then (when >> accessor is logged, it >> just does nothing, if it isn't, it connects the >> accessor, >> but tries to do >> some additional work which always fails)? >> >> Herby >> >> >> From memory this is caused by differences between >> VisualWorks >> and Pharo. >> >> Anyway, it is discussed and resolved in: >> >> http://forum.world.st/Glorp-SQLite3-issue-td4899792.html >> <http://forum.world.st/Glorp-SQLite3-issue-td4899792.html> >> <http://forum.world.st/Glorp-SQLite3-issue-td4899792.html >> <http://forum.world.st/Glorp-SQLite3-issue-td4899792.html>> >> >> >> Doesn't look like solved to me. Anyway, at least I know it >> is known >> for year and no-one seemed to see it as a bug. >> >> I think it is one (you cannot just send queryEncoding where >> no class >> implements it and be fine, imo). >> >> So what is the state of `session login`? Is it meant to be >> used, or >> everyone just took a step down to low-level and uses `accessor >> login` instead? :-( >> >> >> Cheers, >> Alistair >> >> >> Thanks, Herby >> >> >> >> >> >> >> -- >> >> >> >> Guille Polito >> >> >> Research Engineer >> >> French National Center for Scientific Research - _http://www.cnrs.fr_ >> >> >> >> *Web:* _http://guillep.github.io_ >> >> *Phone: *+33 06 52 70 66 13 >> > >

Aug. 5, 2017

Re: [Pharo-users] Best Practices for Bundling Documentation

by Evan Donahue

Hello, The projects are a logic programming and machine learning system respectively, so they probably warrant more involved tutorial-style documentation. I will take a look at the Pillar docs, but just to think ahead a bit, assuming I write up some docs in Pillar, what would be the best way to distribute those? Can they be packaged with the code or would the docs be outside the image? If outside, where do people tend to host them? Thanks, Evan -- View this message in context: http://forum.world.st/Best-Practices-for-Bundling-Documentation-tp4958788p4… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 5, 2017

Re: [Pharo-users] Glorp: `session login` fails for Garage SQLite

by Herby VojÄÃk

Guillermo Polito wrote: > AFAIR, PharoDatabaseAccessor was meant to work with SqueakDBX/DBXTalk > driver. No other driver should use it. At the time Garage did not even > exist. > > So I'd say that you should not use PharoDatabaseAccessor with another > driver than the one it was originally mean to? I do not know exactly > your setup, I was not following this thread. > > Really I cannot tell much more. This was really long time ago. Great to know! I am not using it consciously, though. System somehow selects it and uses it in the background (I just do MyDescriptorSystem sessionForLogin: myLoginObject; and before that I set GarageGlorpDrive to be the default). This seems to be the actual fix (make Glorp with Garage not use PharoDatabaseAccessor). Herby > > On Sun, Aug 6, 2017 at 12:20 AM, Herby VojÄÃk <herby(a)mailbox.sk > <mailto:herby@mailbox.sk>> wrote: > > Esteban A. Maringolo wrote: > > Herby, > > I regularly use `session login`, but I don't use SQLite in > Pharo, but I > do in VisualWorks and it works just fine. > Maybe if there is a bug we should fix it. Even with a no-op method. > > Regards! > > Esteban A. Maringolo > > > It's hard. The problem is > > PharoDatabaseAccessor >> encoding > ^self connection queryEncoding > > which overrides parent, which is atm: > > encoding > "The connection is specific to the dialect; some dialects will need > to override this method." > > ^connection encoding > > The former was added at GuillermoPolito.73 back in 2011 (and the > latter was the same back then). It probably fixed something, but I > don't see any implementors of queryEncoding atm (definitely not in > Garage). From the diff it is clear lots of databases and drivers > have gone. Now, why was it change for Pharo (and does it need to be > changed in 2017)? > > Ccing Guillermo Polito. > > Herby > > P.S.: I wonder how it is that no one actually had problem with this? > This predictably fails on `session login` on pharo, unless > queryEncoding is somehow magically present without seeing it in > source code for other platforms? > > > 2017-08-05 15:52 GMT-03:00 Herby VojÄÃk <herby(a)mailbox.sk > <mailto:herby@mailbox.sk> > <mailto:herby@mailbox.sk <mailto:herby@mailbox.sk>>>: > > Alistair Grant wrote: > > Hi Herby, > > On 5 August 2017 at 18:09, Herby > VojÄÃk<herby(a)mailbox.sk <mailto:herby@mailbox.sk> > <mailto:herby@mailbox.sk <mailto:herby@mailbox.sk>>> wrote: > > Hello! > > First of all, what is preferred way to (first time) > login > into database? I > had the impression that `aDatabaseAccessor login` > is sorta > low-level, and > one should do `session login` (after all, it is > session you > get to work > with, not an accessor). > > But with Garage SQLite, `session login`, when > accessor is > not logged, always > fails with "MessageNotUnderstood: > GASqlite3Driver>>queryEncoding". > > Should one not use `session login` at all, then (when > accessor is logged, it > just does nothing, if it isn't, it connects the > accessor, > but tries to do > some additional work which always fails)? > > Herby > > > From memory this is caused by differences between > VisualWorks > and Pharo. > > Anyway, it is discussed and resolved in: > > http://forum.world.st/Glorp-SQLite3-issue-td4899792.html > <http://forum.world.st/Glorp-SQLite3-issue-td4899792.html> > <http://forum.world.st/Glorp-SQLite3-issue-td4899792.html > <http://forum.world.st/Glorp-SQLite3-issue-td4899792.html>> > > > Doesn't look like solved to me. Anyway, at least I know it > is known > for year and no-one seemed to see it as a bug. > > I think it is one (you cannot just send queryEncoding where > no class > implements it and be fine, imo). > > So what is the state of `session login`? Is it meant to be > used, or > everyone just took a step down to low-level and uses `accessor > login` instead? :-( > > > Cheers, > Alistair > > > Thanks, Herby > > > > > > > -- > > > > Guille Polito > > > Research Engineer > > French National Center for Scientific Research - _http://www.cnrs.fr_ > > > > *Web:* _http://guillep.github.io_ > > *Phone: *+33 06 52 70 66 13 >

Aug. 5, 2017

Re: [Pharo-users] Glorp: `session login` fails for Garage SQLite

by Herby VojÄÃk

Esteban A. Maringolo wrote: > Which version of Pharo, Glorp and SQLite are you using? As for SQLite dll, I don't know (does it change the fact if queryEncoding method is present?). Pharo is 6.1, Glorp, Garage etc. are #stable loaded from Pharo60 catalog (see attachment). Herby > > > Esteban A. Maringolo > > > 2017-08-05 19:20 GMT-03:00 Herby VojÄÃk<herby(a)mailbox.sk>: >> Esteban A. Maringolo wrote: >>> Herby, >>> >>> I regularly use `session login`, but I don't use SQLite in Pharo, but I >>> do in VisualWorks and it works just fine. >>> Maybe if there is a bug we should fix it. Even with a no-op method. >>> >>> Regards! >>> >>> Esteban A. Maringolo >> >> It's hard. The problem is >> >> PharoDatabaseAccessor>> encoding >> ^self connection queryEncoding >> >> which overrides parent, which is atm: >> >> encoding >> "The connection is specific to the dialect; some dialects will need >> to override this method." >> >> ^connection encoding >> >> The former was added at GuillermoPolito.73 back in 2011 (and the latter was >> the same back then). It probably fixed something, but I don't see any >> implementors of queryEncoding atm (definitely not in Garage). From the diff >> it is clear lots of databases and drivers have gone. Now, why was it change >> for Pharo (and does it need to be changed in 2017)? >> >> Ccing Guillermo Polito. >> >> Herby >> >> P.S.: I wonder how it is that no one actually had problem with this? This >> predictably fails on `session login` on pharo, unless queryEncoding is >> somehow magically present without seeing it in source code for other >> platforms? >> >>> 2017-08-05 15:52 GMT-03:00 Herby VojÄÃk<herby(a)mailbox.sk >>> <mailto:herby@mailbox.sk>>: >>> >>> Alistair Grant wrote: >>> >>> Hi Herby, >>> >>> On 5 August 2017 at 18:09, Herby VojÄÃk<herby(a)mailbox.sk >>> <mailto:herby@mailbox.sk>> wrote: >>> >>> Hello! >>> >>> First of all, what is preferred way to (first time) login >>> into database? I >>> had the impression that `aDatabaseAccessor login` is sorta >>> low-level, and >>> one should do `session login` (after all, it is session you >>> get to work >>> with, not an accessor). >>> >>> But with Garage SQLite, `session login`, when accessor is >>> not logged, always >>> fails with "MessageNotUnderstood: >>> GASqlite3Driver>>queryEncoding". >>> >>> Should one not use `session login` at all, then (when >>> accessor is logged, it >>> just does nothing, if it isn't, it connects the accessor, >>> but tries to do >>> some additional work which always fails)? >>> >>> Herby >>> >>> >>> From memory this is caused by differences between VisualWorks >>> and Pharo. >>> >>> Anyway, it is discussed and resolved in: >>> >>> http://forum.world.st/Glorp-SQLite3-issue-td4899792.html >>> <http://forum.world.st/Glorp-SQLite3-issue-td4899792.html> >>> >>> >>> Doesn't look like solved to me. Anyway, at least I know it is known >>> for year and no-one seemed to see it as a bug. >>> >>> I think it is one (you cannot just send queryEncoding where no class >>> implements it and be fine, imo). >>> >>> So what is the state of `session login`? Is it meant to be used, or >>> everyone just took a step down to low-level and uses `accessor >>> login` instead? :-( >>> >>> >>> Cheers, >>> Alistair >>> >>> >>> Thanks, Herby >>> >>> >> >

Aug. 5, 2017

Re: [Pharo-users] Glorp: `session login` fails for Garage SQLite

by Guillermo Polito

AFAIR, PharoDatabaseAccessor was meant to work with SqueakDBX/DBXTalk driver. No other driver should use it. At the time Garage did not even exist. So I'd say that you should not use PharoDatabaseAccessor with another driver than the one it was originally mean to? I do not know exactly your setup, I was not following this thread. Really I cannot tell much more. This was really long time ago. On Sun, Aug 6, 2017 at 12:20 AM, Herby VojÄÃk <herby(a)mailbox.sk> wrote: > Esteban A. Maringolo wrote: > >> Herby, >> >> I regularly use `session login`, but I don't use SQLite in Pharo, but I >> do in VisualWorks and it works just fine. >> Maybe if there is a bug we should fix it. Even with a no-op method. >> >> Regards! >> >> Esteban A. Maringolo >> > > It's hard. The problem is > > PharoDatabaseAccessor >> encoding > ^self connection queryEncoding > > which overrides parent, which is atm: > > encoding > "The connection is specific to the dialect; some dialects will > need to override this method." > > ^connection encoding > > The former was added at GuillermoPolito.73 back in 2011 (and the latter > was the same back then). It probably fixed something, but I don't see any > implementors of queryEncoding atm (definitely not in Garage). From the diff > it is clear lots of databases and drivers have gone. Now, why was it change > for Pharo (and does it need to be changed in 2017)? > > Ccing Guillermo Polito. > > Herby > > P.S.: I wonder how it is that no one actually had problem with this? This > predictably fails on `session login` on pharo, unless queryEncoding is > somehow magically present without seeing it in source code for other > platforms? > > >> 2017-08-05 15:52 GMT-03:00 Herby VojÄÃk <herby(a)mailbox.sk >> <mailto:herby@mailbox.sk>>: >> >> Alistair Grant wrote: >> >> Hi Herby, >> >> On 5 August 2017 at 18:09, Herby VojÄÃk<herby(a)mailbox.sk >> <mailto:herby@mailbox.sk>> wrote: >> >> Hello! >> >> First of all, what is preferred way to (first time) login >> into database? I >> had the impression that `aDatabaseAccessor login` is sorta >> low-level, and >> one should do `session login` (after all, it is session you >> get to work >> with, not an accessor). >> >> But with Garage SQLite, `session login`, when accessor is >> not logged, always >> fails with "MessageNotUnderstood: >> GASqlite3Driver>>queryEncoding". >> >> Should one not use `session login` at all, then (when >> accessor is logged, it >> just does nothing, if it isn't, it connects the accessor, >> but tries to do >> some additional work which always fails)? >> >> Herby >> >> >> From memory this is caused by differences between VisualWorks >> and Pharo. >> >> Anyway, it is discussed and resolved in: >> >> http://forum.world.st/Glorp-SQLite3-issue-td4899792.html >> <http://forum.world.st/Glorp-SQLite3-issue-td4899792.html> >> >> >> Doesn't look like solved to me. Anyway, at least I know it is known >> for year and no-one seemed to see it as a bug. >> >> I think it is one (you cannot just send queryEncoding where no class >> implements it and be fine, imo). >> >> So what is the state of `session login`? Is it meant to be used, or >> everyone just took a step down to low-level and uses `accessor >> login` instead? :-( >> >> >> Cheers, >> Alistair >> >> >> Thanks, Herby >> >> >> > -- Guille Polito Research Engineer French National Center for Scientific Research - *http://www.cnrs.fr* <http://www.cnrs.fr> *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Aug. 5, 2017

Re: [Pharo-users] Glorp: `session login` fails for Garage SQLite

by Esteban A. Maringolo

Which version of Pharo, Glorp and SQLite are you using? Esteban A. Maringolo 2017-08-05 19:20 GMT-03:00 Herby VojÄÃk <herby(a)mailbox.sk>: > Esteban A. Maringolo wrote: >> >> Herby, >> >> I regularly use `session login`, but I don't use SQLite in Pharo, but I >> do in VisualWorks and it works just fine. >> Maybe if there is a bug we should fix it. Even with a no-op method. >> >> Regards! >> >> Esteban A. Maringolo > > > It's hard. The problem is > > PharoDatabaseAccessor >> encoding > ^self connection queryEncoding > > which overrides parent, which is atm: > > encoding > "The connection is specific to the dialect; some dialects will need > to override this method." > > ^connection encoding > > The former was added at GuillermoPolito.73 back in 2011 (and the latter was > the same back then). It probably fixed something, but I don't see any > implementors of queryEncoding atm (definitely not in Garage). From the diff > it is clear lots of databases and drivers have gone. Now, why was it change > for Pharo (and does it need to be changed in 2017)? > > Ccing Guillermo Polito. > > Herby > > P.S.: I wonder how it is that no one actually had problem with this? This > predictably fails on `session login` on pharo, unless queryEncoding is > somehow magically present without seeing it in source code for other > platforms? > >> >> 2017-08-05 15:52 GMT-03:00 Herby VojÄÃk <herby(a)mailbox.sk >> <mailto:herby@mailbox.sk>>: >> >> Alistair Grant wrote: >> >> Hi Herby, >> >> On 5 August 2017 at 18:09, Herby VojÄÃk<herby(a)mailbox.sk >> <mailto:herby@mailbox.sk>> wrote: >> >> Hello! >> >> First of all, what is preferred way to (first time) login >> into database? I >> had the impression that `aDatabaseAccessor login` is sorta >> low-level, and >> one should do `session login` (after all, it is session you >> get to work >> with, not an accessor). >> >> But with Garage SQLite, `session login`, when accessor is >> not logged, always >> fails with "MessageNotUnderstood: >> GASqlite3Driver>>queryEncoding". >> >> Should one not use `session login` at all, then (when >> accessor is logged, it >> just does nothing, if it isn't, it connects the accessor, >> but tries to do >> some additional work which always fails)? >> >> Herby >> >> >> From memory this is caused by differences between VisualWorks >> and Pharo. >> >> Anyway, it is discussed and resolved in: >> >> http://forum.world.st/Glorp-SQLite3-issue-td4899792.html >> <http://forum.world.st/Glorp-SQLite3-issue-td4899792.html> >> >> >> Doesn't look like solved to me. Anyway, at least I know it is known >> for year and no-one seemed to see it as a bug. >> >> I think it is one (you cannot just send queryEncoding where no class >> implements it and be fine, imo). >> >> So what is the state of `session login`? Is it meant to be used, or >> everyone just took a step down to low-level and uses `accessor >> login` instead? :-( >> >> >> Cheers, >> Alistair >> >> >> Thanks, Herby >> >> > >

Aug. 5, 2017