January 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Databases with full text search support

by Miguel CobÃ¡

El jue, 27-01-2011 a las 18:24 -0500, Dmitri Zagidulin escribiÃ³: > As far as bindings for MongoDB, if you're referring to > http://www.squeaksource.com/MongoTalk - though it's an excellent > start, it is not quite production ready. In that - > only the MongoDB equivalents of 'select' and 'insert' have been > implemented, but not update or delete. I'm working on implementing > those operations right now & submitting a patch, and should have a > post up about it in a > couple of weeks. But Mongo is not yet in the running, for full text search. Oh, good to know. -- Miguel CobÃ¡ http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx

Jan. 28, 2011

Re: [Pharo-project] Databases with full text search support

by Dmitri Zagidulin

As far as bindings for MongoDB, if you're referring to http://www.squeaksource.com/MongoTalk - though it's an excellent start, it is not quite production ready. In that - only the MongoDB equivalents of 'select' and 'insert' have been implemented, but not update or delete. I'm working on implementing those operations right now & submitting a patch, and should have a post up about it in a couple of weeks. But Mongo is not yet in the running, for full text search. Dmitri Zagidulin http://smalltalkzen.wordpress.com On Thu, Jan 27, 2011 at 2:58 PM, Miguel CobÃ¡ <miguel.coba(a)gmail.com> wrote: > There isn't a full solution that I know of, but maybe you can use lucene > to store index info outside smalltalk and use the references to search > for the real smalltal objects. > > There are also bindings for several nosql databases for lucene and solr > like mongo db and cassandra and there are bindings in smalltalk for > mondodb and cassandra. > > Cheers > > El jue, 27-01-2011 a las 20:48 +0100, laurent laffont escribiÃ³: >> Hi, >> >> >> I need to have full text indexing and searching over a 3-5 million >> documents. Actually the products I work on are written in PHP - >> MySQL. >> >> >> What would you use (open source - mandatory - our products are open >> source) in Smalltalk world Â to do this ? >> >> Laurent Laffont - @lolgzs >> >> Pharo Smalltalk Screencasts: http://www.pharocasts.com/ >> Blog: http://magaloma.blogspot.com/ >> > > -- > Miguel CobÃ¡ > http://twitter.com/MiguelCobaMtz > http://miguel.leugim.com.mx > > > > >

Jan. 27, 2011

Re: [Pharo-project] About FileSystem (probably not for 1.3)

by Dale Henrichs

On 01/27/2011 03:00 PM, Lukas Renggli wrote: >> I started to merge some of your changes to FS. > > I already merged most of the changes of Max into the main code. > >> Now I was wondering about this one: >> ***for my work on GitFS I needed a resumable exception (alternatively an ifPresent block would have done the trick but that would have ment more meddling with Filesystem) to delete existing files when copying. The following changes are a result of introducing this exception to the copy methods. >> *added class FSFileExistsResumbale and its superclass FSFilesystemException to support the changes to the copy methods >> *#copy:to: signals FSFileExistsResumbale instead of FSFileExists >> *FSCopyVisitor>>copyDirectory uses #ensureDirectory instead of #createDirectory >> *needed to change FSFilesystemTest>>testCopyDestExists to expect FSFileExistsResumable >> *FSReference>>basicCopyTo: signals FSFileExistsResumable instead of FSFileExists >> >> Could you explain us a bit more? > > This is not something that should go into the main code. If I remember > correctly this was a quick hack to avoid some problems in GitFS. > > Lukas > At the time I ported FileSystem to GemStone (4 months ago?), I started with the packages in Lukas' repository... Dale

Jan. 27, 2011

Re: [Pharo-project] About FileSystem (probably not for 1.3)

by Lukas Renggli

> I started to merge some of your changes to FS. I already merged most of the changes of Max into the main code. > Now I was wondering about this one: > ***for my work on GitFS I needed a resumable exception (alternatively an ifPresent block would have done the trick but that would have ment more meddling with Filesystem) to delete existing files when copying. The following changes are a result of introducing this exception to the copy methods. > *added class FSFileExistsResumbale and its superclass FSFilesystemException to support the changes to the copy methods > *#copy:to: signals FSFileExistsResumbale instead of FSFileExists > *FSCopyVisitor>>copyDirectory uses #ensureDirectory instead of #createDirectory > *needed to change FSFilesystemTest>>testCopyDestExists to expect FSFileExistsResumable > *FSReference>>basicCopyTo: signals FSFileExistsResumable instead of FSFileExists > > Could you explain us a bit more? This is not something that should go into the main code. If I remember correctly this was a quick hack to avoid some problems in GitFS. Lukas -- Lukas Renggli www.lukas-renggli.ch

Jan. 27, 2011

Re: [Pharo-project] About FileSystem (probably not for 1.3)

by Dale Henrichs

Sounds good ... I'll work through the changes that I've made and try to extract out the goodness and then provide suggested changes (in the form of an mcz file you can merge if the changes make sense to you)... BTW, I used the FileSystem port with a Monticello port (replacing all of the FileDirectory stuff with FileSystem calls) and the Monticello port was based on a fairly recent Pharo version of Monticello:) Dale On 01/27/2011 01:34 PM, StÃ©phane Ducasse wrote: > I'm. :) > I do not want differences for the shake for them. I want an excellent system. > I'm working on PharoTaskForces so if you can merge step by step it would be great. > > Stef > > > On Jan 27, 2011, at 10:31 PM, Dale Henrichs wrote: > >> Stef, >> >> I have ported FileSystem to GemStone, but I had to make a number of changes that were necessary to improve the portability (at least for GemStone) ... It would be a bit of work for me to extract the changes, but I'd be willing to do it if you were interested in incorporated some of them (if not all) ... >> >> Dale >> >> On 01/27/2011 12:58 PM, StÃ©phane Ducasse wrote: >>> Hi max >>> >>> I started to merge some of your changes to FS. >>> Now I was wondering about this one: >>> >>> ***for my work on GitFS I needed a resumable exception (alternatively an ifPresent block would have done the trick but that would have ment more meddling with Filesystem) to delete existing files when copying. The following changes are a result of introducing this exception to the copy methods. >>> *added class FSFileExistsResumbale and its superclass FSFilesystemException to support the changes to the copy methods >>> *#copy:to: signals FSFileExistsResumbale instead of FSFileExists >>> *FSCopyVisitor>>copyDirectory uses #ensureDirectory instead of #createDirectory >>> *needed to change FSFilesystemTest>>testCopyDestExists to expect FSFileExistsResumable >>> *FSReference>>basicCopyTo: signals FSFileExistsResumable instead of FSFileExists >>> >>> Could you explain us a bit more? >>> >>> Stef >>>> >>> >> >

Jan. 27, 2011

Re: [Pharo-project] Databases with full text search support

by Levente Uzonyi

On Thu, 27 Jan 2011, laurent laffont wrote: > Hi, > > I need to have full text indexing and searching over a 3-5 million > documents. Actually the products I work on are written in PHP - MySQL. > > What would you use (open source - mandatory - our products are open source) > in Smalltalk world to do this ? PostgreSQL of course. It's not Smalltalk, but there are at least 3 different bindings for it and it has built in full text indexing: http://www.postgresql.org/docs/current/static/textsearch.html . Levente > > Laurent Laffont - @lolgzs <http://twitter.com/#!/lolgzs> > > Pharo Smalltalk Screencasts: http://www.pharocasts.com/ > Blog: http://magaloma.blogspot.com/ >

Jan. 27, 2011

Re: [Pharo-project] SystemTracer

by Levente Uzonyi

On Thu, 27 Jan 2011, Benjamin wrote: > It works for PharoCore-1.1-11196-UNSTABLE.1 but it seems to be the only version where it works :S > > Does someone know why ? It doesn't support Cog's image format. Try an image with the original Squeak format. You can convert your image with the latest SqueakVM. Only the unix VM was released with this feature yet, so you can use that http://squeakvm.org/unix/ or build a VM for your favorite platform. Levente > > > Thanks, > > Ben > > On Jan 27, 2011, at 3:36 PM, Benjamin wrote: > >> Hello guys, >> >> for one of my projects, I'm trying to use SystemTracer to create anew image, but it appears that it doesn't work on Pharo ... >> I can create a new image, but I can't open it. I've tried with an older VM (Squeak 3.8.18beta1U), but it's the same ... >> >> >> Did someone already have this problem ? Does someone have a solution ? >> >> >> >> Thanks in advance, >> >> Ben > >

Jan. 27, 2011

Re: [Pharo-project] About FileSystem (probably not for 1.3)

by StÃ©phane Ducasse

I'm. :) I do not want differences for the shake for them. I want an excellent system. I'm working on PharoTaskForces so if you can merge step by step it would be great. Stef On Jan 27, 2011, at 10:31 PM, Dale Henrichs wrote: > Stef, > > I have ported FileSystem to GemStone, but I had to make a number of changes that were necessary to improve the portability (at least for GemStone) ... It would be a bit of work for me to extract the changes, but I'd be willing to do it if you were interested in incorporated some of them (if not all) ... > > Dale > > On 01/27/2011 12:58 PM, StÃ©phane Ducasse wrote: >> Hi max >> >> I started to merge some of your changes to FS. >> Now I was wondering about this one: >> >> ***for my work on GitFS I needed a resumable exception (alternatively an ifPresent block would have done the trick but that would have ment more meddling with Filesystem) to delete existing files when copying. The following changes are a result of introducing this exception to the copy methods. >> *added class FSFileExistsResumbale and its superclass FSFilesystemException to support the changes to the copy methods >> *#copy:to: signals FSFileExistsResumbale instead of FSFileExists >> *FSCopyVisitor>>copyDirectory uses #ensureDirectory instead of #createDirectory >> *needed to change FSFilesystemTest>>testCopyDestExists to expect FSFileExistsResumable >> *FSReference>>basicCopyTo: signals FSFileExistsResumable instead of FSFileExists >> >> Could you explain us a bit more? >> >> Stef >>> >> >

Jan. 27, 2011

Re: [Pharo-project] About FileSystem (probably not for 1.3)

by Dale Henrichs

Stef, I have ported FileSystem to GemStone, but I had to make a number of changes that were necessary to improve the portability (at least for GemStone) ... It would be a bit of work for me to extract the changes, but I'd be willing to do it if you were interested in incorporated some of them (if not all) ... Dale On 01/27/2011 12:58 PM, StÃ©phane Ducasse wrote: > Hi max > > I started to merge some of your changes to FS. > Now I was wondering about this one: > > ***for my work on GitFS I needed a resumable exception (alternatively an ifPresent block would have done the trick but that would have ment more meddling with Filesystem) to delete existing files when copying. The following changes are a result of introducing this exception to the copy methods. > *added class FSFileExistsResumbale and its superclass FSFilesystemException to support the changes to the copy methods > *#copy:to: signals FSFileExistsResumbale instead of FSFileExists > *FSCopyVisitor>>copyDirectory uses #ensureDirectory instead of #createDirectory > *needed to change FSFilesystemTest>>testCopyDestExists to expect FSFileExistsResumable > *FSReference>>basicCopyTo: signals FSFileExistsResumable instead of FSFileExists > > Could you explain us a bit more? > > Stef >> >

Jan. 27, 2011

Re: [Pharo-project] Issue 3604 in pharo: Timespan created from Date>>to: missing last date

by pharo＠googlecode.com

Comment #1 on issue 3604 by edoua...(a)gmail.com: Timespan created from Date>>to: missing last date http://code.google.com/p/pharo/issues/detail?id=3604 Opps - Simplest version should of course read (Date today to: Date today) includes: Date today. " false "

Jan. 27, 2011