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

Voyage: save Date, get back DateAndTime - bug?

by Sabine KnÃ¶fel

Hi Esteban, All, when saving an instance of *Date* within an attribute with voyage into Mongo and doing VOMongoRepository allInstancesDo: #reset. then loading the object back from database, I get an inst of *DateAndTime* in this attribute. Of course, I can "hack" by the tools you gave me :-) it but I ask myself if this is a bug or by intent. Regards Sabine -- View this message in context: http://forum.world.st/Voyage-save-Date-get-back-DateAndTime-bug-tp4703601.h… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 14, 2013

Re: [Pharo-users] Voyage: Circular references

by Sabine KnÃ¶fel

Hi Esteban, thanks, this works fine now! You also answered my next question how to define an attribute as transient -> with VOMongoTransientDescription :) Your blog posts http://smallworks.com.ar/web/blog?_k=c9RiCz1d5w-0XSbp are very helpful to start. Do you have more information/documentation for voyage? Regards Sabine -- View this message in context: http://forum.world.st/Voyage-Circular-references-tp4691940p4703493.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 13, 2013

Re: [Pharo-users] Voyage: Circular references

by Esteban Lorenzano

Hi Sabine, Sadly there is no automatic solution for your problem. I managed to resolve that by hacking the mongo description this way: Trip class>> isVoyageRoot = true Day class>> isVoyageRoot = false VehicleTrip class>> isVoyageRoot = false Now, the trick is that since the document will be something like: Trip { days { Day { VehicleTrip { ... day} VehicleTrip { ... day} } } } (that's of course, pseudo coding heavily ;) ) Actually, since all VehicleTrips will be part of Day subdocument, you do not need to store them. What you really need is to have the back-reference when you reconstruct the document You can achieve that by declaring transient the #day attribute of VehicleTrip and setting the day back when you read Day from the database: VehicleTrip class>>mongoDay <mongoDescription> ^ VOMongoTransientDescription new attributeName: 'day'; yourself Day class>>mongoVehicleTrips <mongoDescription> ^VOMongoToManyDescription new attributeName: 'vehicleTrips'; accessor: (MAPluggableAccessor read: [ :day | day vehicleTrips ] write: [ :day :trips | trips do: [ :each | each day: day ]. day vehicleTrips: trips ]); yourself I think that will solve your embedded-cyclic problem. yes... it is a bit hacky, but it works perfectly :) Cheers, Esteban On Aug 12, 2013, at 11:33 AM, Sabine KnÃ¶fel <sabine.knoefel(a)gmail.com> wrote: > Hi Esteban, > > thank you for the solution with the VOMongoToOneDescription. > This works perfect for me. > > I have to come back to the circular references. > I am not sure if this is a bug. > > I have the following model: > > Trip ->> Day <->> VehicleTrip > > One Trip has N Days. > One Day has N VehicleTrips. > The VehicleTrip points back to its Day. > The Trip is voyageRoot. > > But I dont want Day or VehicleTrip to be voyageRoot, too. > (In my opinion this does not make sense). > > If I try to save the trip, I get the endless loop. > Attention, the Image freezes then. :-) > > How would you solve this? Also with the VOMongoToOneDescription solution? > You can reproduce it with the fileout below. > > Regards > Sabine > > This is the fileout: > > Object subclass: #Day > instanceVariableNames: 'date vehicleTrips' > classVariableNames: '' > poolDictionaries: '' > category: 'RKA24-Demo'! > > !Day methodsFor: 'accessing' stamp: 'sabineknoefel 8/12/2013 11:13'! > date: anObject > > date := anObject! ! > > !Day methodsFor: 'accessing' stamp: 'sabineknoefel 8/12/2013 11:15'! > vehicleTrips: anObject > > vehicleTrips := anObject! ! > > > Object subclass: #VehicleTrip > instanceVariableNames: 'day description' > classVariableNames: '' > poolDictionaries: '' > category: 'RKA24-Demo'! > > !VehicleTrip methodsFor: 'accessing' stamp: 'sabineknoefel 8/12/2013 11:13'! > day: anObject > > day := anObject! ! > > !VehicleTrip methodsFor: 'accessing' stamp: 'sabineknoefel 8/12/2013 11:14'! > description: anObject > > description := anObject! ! > > > Object subclass: #Trip > instanceVariableNames: 'days description' > classVariableNames: '' > poolDictionaries: '' > category: 'RKA24-Demo'! > > !Trip methodsFor: 'accessing' stamp: 'sabineknoefel 8/12/2013 11:14'! > days: anObject > > days := anObject! ! > > !Trip methodsFor: 'accessing' stamp: 'sabineknoefel 8/12/2013 10:12'! > description: anObject > > description := anObject! ! > > "-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- "! > > Trip class > instanceVariableNames: ''! > > !Trip class methodsFor: 'as yet unclassified' stamp: 'sabineknoefel > 8/12/2013 11:15'! > demo > |theTrip theDay theVehicleTrip| > theTrip := Trip new description: 'Trip to Munic'. > theDay := Day new date: Date today. > theVehicleTrip := VehicleTrip new description: 'with car to fair'. > theVehicleTrip day: theDay. > theTrip days: (OrderedCollection with: theDay). > theDay vehicleTrips: (OrderedCollection with: theVehicleTrip ). > > theTrip halt save ! ! > > !Trip class methodsFor: 'as yet unclassified' stamp: 'sabineknoefel > 8/12/2013 09:47'! > isVoyageRoot > ^true! ! > > > > > > |theTrip theDay theVehicleTrip| > theTrip := Trip new description: 'Trip to Munic'. > theDay := Day new date: Date today. > theVehicleTrip := VehicleTrip new description: 'with car to fair'. > theVehicleTrip day: theDay. > theTrip days: (OrderedCollection with: theDay). > theDay vehicleTrips: (OrderedCollection with: theVehicleTrip ). > > theTrip inspect > > > > -- > View this message in context: http://forum.world.st/Voyage-Circular-references-tp4691940p4703303.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

Aug. 12, 2013

Re: [Pharo-users] Databases for Pharo that do not use FFI

by Pierce Ng

On Sat, Aug 10, 2013 at 11:44:06PM +1000, vinref(a)gmail.com wrote: > VoyageMongo looks interesting. PostgreSQL is supported too. Do either of > these work through FFI? On SqueakSource, PostgresV2, PostgresV3, MySQL and StdbCore (for MySQL) are pure Smalltalk implementations of the respective wire protocols. -- Pierce Ng http://samadhiweb.com/blog/

Aug. 12, 2013

Re: [Pharo-users] Git filetree workflow

by Martin Dias

On Wed, Jul 31, 2013 at 6:27 PM, joerick <joerick(a)mac.com> wrote: > In the Gofer #push case, it's quite strange... some classes end up the > wrong > package, and some don't get output at all. > > It seems to work using Gofer #push when each is in its own repository > folder, and it also works with them all in the same folder when using > Monticello Browser's 'save' button. > > Hi, sorry for the delay: > Perhaps I should try moving to 2.0. Last time we tried there was a package > that hadn't been ported yet, I can't recall what it was... fuel perhaps? > Pharo 2 image comes with Fuel already loaded. It's fuel 1.9, so you might need to migrate your fuel files, or to load another fuel version. MartÃn

Aug. 12, 2013

Re: [Pharo-users] Voyage: Circular references

by Sabine KnÃ¶fel

Hi Esteban, thank you for the solution with the VOMongoToOneDescription. This works perfect for me. I have to come back to the circular references. I am not sure if this is a bug. I have the following model: Trip ->> Day <->> VehicleTrip One Trip has N Days. One Day has N VehicleTrips. The VehicleTrip points back to its Day. The Trip is voyageRoot. But I dont want Day or VehicleTrip to be voyageRoot, too. (In my opinion this does not make sense). If I try to save the trip, I get the endless loop. Attention, the Image freezes then. :-) How would you solve this? Also with the VOMongoToOneDescription solution? You can reproduce it with the fileout below. Regards Sabine This is the fileout: Object subclass: #Day instanceVariableNames: 'date vehicleTrips' classVariableNames: '' poolDictionaries: '' category: 'RKA24-Demo'! !Day methodsFor: 'accessing' stamp: 'sabineknoefel 8/12/2013 11:13'! date: anObject date := anObject! ! !Day methodsFor: 'accessing' stamp: 'sabineknoefel 8/12/2013 11:15'! vehicleTrips: anObject vehicleTrips := anObject! ! Object subclass: #VehicleTrip instanceVariableNames: 'day description' classVariableNames: '' poolDictionaries: '' category: 'RKA24-Demo'! !VehicleTrip methodsFor: 'accessing' stamp: 'sabineknoefel 8/12/2013 11:13'! day: anObject day := anObject! ! !VehicleTrip methodsFor: 'accessing' stamp: 'sabineknoefel 8/12/2013 11:14'! description: anObject description := anObject! ! Object subclass: #Trip instanceVariableNames: 'days description' classVariableNames: '' poolDictionaries: '' category: 'RKA24-Demo'! !Trip methodsFor: 'accessing' stamp: 'sabineknoefel 8/12/2013 11:14'! days: anObject days := anObject! ! !Trip methodsFor: 'accessing' stamp: 'sabineknoefel 8/12/2013 10:12'! description: anObject description := anObject! ! "-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- "! Trip class instanceVariableNames: ''! !Trip class methodsFor: 'as yet unclassified' stamp: 'sabineknoefel 8/12/2013 11:15'! demo |theTrip theDay theVehicleTrip| theTrip := Trip new description: 'Trip to Munic'. theDay := Day new date: Date today. theVehicleTrip := VehicleTrip new description: 'with car to fair'. theVehicleTrip day: theDay. theTrip days: (OrderedCollection with: theDay). theDay vehicleTrips: (OrderedCollection with: theVehicleTrip ). theTrip halt save ! ! !Trip class methodsFor: 'as yet unclassified' stamp: 'sabineknoefel 8/12/2013 09:47'! isVoyageRoot ^true! ! |theTrip theDay theVehicleTrip| theTrip := Trip new description: 'Trip to Munic'. theDay := Day new date: Date today. theVehicleTrip := VehicleTrip new description: 'with car to fair'. theVehicleTrip day: theDay. theTrip days: (OrderedCollection with: theDay). theDay vehicleTrips: (OrderedCollection with: theVehicleTrip ). theTrip inspect -- View this message in context: http://forum.world.st/Voyage-Circular-references-tp4691940p4703303.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 12, 2013

Re: [Pharo-users] Pharo-users Digest, Vol 4, Issue 23

by vinref＠gmail.com

Thank you Mariano and Stephane. I am going to look at VoyageMongo and PostgreSQL first.

Aug. 10, 2013

Re: [Pharo-users] Databases for Pharo that do not use FFI

by Dale K. Henrichs

GemStone's GCI library uses FFI, but the GCI layer has an option to make non-blocking FFI calls (you end up polling for response) so the vm is free to spin away while polling ... unfortunately, the current GCI API is also single threaded (we're planning to change this in an upcoming release) so you can make only one concurrent non-blocking call. Dale ----- Original Message ----- | From: vinref(a)gmail.com | To: pharo-users(a)lists.pharo.org | Sent: Saturday, August 10, 2013 6:44:06 AM | Subject: [Pharo-users] Databases for Pharo that do not use FFI | | Hello | | I have been tinkering with Pharo long enough now to contemplate | writing a "serious" applications with it. An important consideration | is databases. I have been looking at SQLite but realise since it | works through FFI it probably blocks the VM whilst processing a | query. Is this correct? | | VoyageMongo looks interesting. PostgreSQL is supported too. Do either | of | these work through FFI? | | Many thanks in advance. | |

Aug. 10, 2013

Re: [Pharo-users] Databases for Pharo that do not use FFI

by Mariano Martinez Peck

On Sat, Aug 10, 2013 at 12:46 PM, StÃ©phane Ducasse < stephane.ducasse(a)inria.fr> wrote: > > > Hello > > > > I have been tinkering with Pharo long enough now to contemplate writing > a "serious" applications with it. An important consideration is databases. > > Esteban will start to work on the threaded vm with eliot for such typical > case. > > That would be great. There are some big players like Oracle whose library does not support async queries :( > > I have been looking at SQLite but realise since it works through FFI it > probably blocks the VM whilst processing a query. Is this correct? > > > > VoyageMongo looks interesting. PostgreSQL is supported too. Do either of > > these work through FFI? > > > > Many thanks in advance. > > > > > -- Mariano http://marianopeck.wordpress.com

Aug. 10, 2013

Re: [Pharo-users] Databases for Pharo that do not use FFI

by StÃ©phane Ducasse

> Hello > > I have been tinkering with Pharo long enough now to contemplate writing a "serious" applications with it. An important consideration is databases. Esteban will start to work on the threaded vm with eliot for such typical case. > I have been looking at SQLite but realise since it works through FFI it probably blocks the VM whilst processing a query. Is this correct? > > VoyageMongo looks interesting. PostgreSQL is supported too. Do either of > these work through FFI? > > Many thanks in advance. >

Aug. 10, 2013