subject:"Re\: \[Pharo\-users\] OmniBase for Pharo 6"

Re: [Pharo-users] OmniBase for Pharo 6

2018-07-28 Thread PBKResearch

Marco

Thanks again. I was apprehensive about using OmniBase for real. With all
green tests I am much happier.

Peter Kenny

-Original Message-
From: Pharo-users  On Behalf Of marco
Sent: 27 July 2018 14:51
To: pharo-users@lists.pharo.org
Subject: Re: [Pharo-users] OmniBase for Pharo 6

Peter,

yes, tested windows (10) and unix/linux (32-bit). It works, green light.

With the 2010 "fix" at least the garbage collection will not work on any OS.

The logic tries to lock the same file twice. 




--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Re: [Pharo-users] OmniBase for Pharo 6

2018-07-27 Thread marco

Peter,

yes, tested windows (10) and unix/linux (32-bit). It works, green light.

With the 2010 "fix" at least the garbage collection will not work on any OS. 
The logic tries to lock the same file twice. 




--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Re: [Pharo-users] OmniBase for Pharo 6

2018-07-25 Thread PBKResearch

Marco

 

Thanks for this. Just for curiosity, did you test it just on Windows, or on
other OSs as well. The logic of the Dec 2010 fix was that David Goriseks
original, being developed on Dolphin, could not be guaranteed to work except
on Windows. I only use Windows, so it is just curiosity.

 

BTW, the author of the Dec 2010 fix, sas, is Sebastian Sastre, so
definitely he.

 

Peter Kenny

 

 

From: Pharo-users  On Behalf Of Matias
Maretto
Sent: 25 July 2018 13:34
To: Any question about pharo is welcome 
Subject: Re: [Pharo-users] OmniBase for Pharo 6

 

Marco: thank you for this. A few weeks ago when I was trying to find the
"lock" problem I saw this method but I did not dare to change it; and just
as you said I  been using OminBase with no problem, but never runned the
Garbage Collector, Surely I was going to have a bigger problem in the future
for not running the garbageCollect. 

 

I have just update this method on my project and tried both the
garbageCollect and the reorganize method , both worked fine (win 7 32bits,
later I am going to test on Win 10 64 bits).

 

Thanks again.

 

Matías.

 

 

  _  

De: Pharo-users mailto:pharo-users-boun...@lists.pharo.org> > en nombre de marco
mailto:ma...@omeleon.de> >
Enviado: miércoles, 25 de julio de 2018 10:23 a. m.
Para: pharo-users@lists.pharo.org <mailto:pharo-users@lists.pharo.org> 
Asunto: Re: [Pharo-users] OmniBase for Pharo 6 

 

One serious problem left: OmniBaseTest>>testGC fails.

Have a look at the 2 methods

/ODBContainer>>lockDataFile
"Dec, 2010 sas: this code was relying in evaluating a block that was
happening only in win32
but not in *nix. So now I'm making it wait for the lock and then execute
the code normally
because it seems the intention was the same."
| currentSpace defaultSpace |

activeDataFile waitForAddingLock.
currentSpace := activeDataFile == dataFileA ifTrue: [0] ifFalse: [1].
defaultSpace := objectManager defaultObjectSpace.
currentSpace == defaultSpace
ifFalse:
[defaultSpace == 0
ifTrue:
[dataFileA isNil ifTrue: [dataFileA := ODBObjectStorage
openOn: self dataFileNameA].
activeDataFile := dataFileA]
ifFalse:
[dataFileB isNil ifTrue: [dataFileB := ODBObjectStorage
openOn: self dataFileNameB].
activeDataFile := dataFileB].
^self lockDataFile]


ODBFile>>waitForLockAt: pos length: length whileWaitingDo: aBlock
"Wait for lock at given position.
Evaluate aBlock in each iteration."

"Dec, 2010. sas: evaluating code in each iteration while waiting sounds
weird but whatever.
I think this was designed on the wrong assumption that the OS always
will provide a false
in the first try but what actually happens is that in win32 you always
will
get at least one false but in *nixes you don't do see that happening
(which is totally reasonable).
BEWARE of stupid code relying on this stupid assumption (I've already
patched #lockDataFile because of this)."
   
| startTime currentTime |
(stream lockAt: pos length: length) ifFalse: [
startTime := Time totalSeconds.
[stream lockAt: pos length: length] whileFalse: [
aBlock value.
currentTime := Time totalSeconds.
currentTime - startTime < self timeOutLength
ifFalse: [
ODBLockNotification signal
ifTrue: [startTime := currentTime]
ifFalse: [^ODBCannotLock signal
/

So "sas" did a refactoring in 2010 because he/she thought it is stupid code.
This code change breaks the GarbageCollection of Omnibase.

I reverted the first method to the original code of the Omnibase author,
David Gorisek:

/lockDataFile

| currentSpace defaultSpace |

activeDataFile waitForAddingLockWhileWaitingDo:
[currentSpace := activeDataFile == dataFileA ifTrue: [0] ifFalse: [1].
defaultSpace := objectManager defaultObjectSpace.
currentSpace == defaultSpace
ifFalse:
[defaultSpace == 0
ifTrue:
[dataFileA isNil ifTrue: [dataFileA := ODBObjectStorage
openOn: self dataFileNameA].
activeDataFile := dataFileA]
ifFalse:
[dataFileB isNil ifTrue: [dataFileB := ODBObjectStorage
openOn: self dataFileNameB].
activeDataFile := dataFileB].
^self lockDataFile]]
/ 
I removed the comment of "sas" from the second method. It is wrong.


The garbage collection works again and the test is green. GC is an important
feature of Omnibase.
It creates a new repository/database file and copies the data into the new
file, compressing the data.
It keeps your database compact and clean. If you don't run it (frequently)
your db fil

Re: [Pharo-users] OmniBase for Pharo 6

2018-07-25 Thread Matias Maretto

Marco: thank you for this. A few weeks ago when I was trying to find the "lock" 
problem I saw this method but I did not dare to change it; and just as you said 
I  been using OminBase with no problem, but never runned the Garbage Collector, 
Surely I was going to have a bigger problem in the future for not running the 
garbageCollect.

I have just update this method on my project and tried both the garbageCollect 
and the reorganize method , both worked fine (win 7 32bits, later I am going to 
test on Win 10 64 bits).

Thanks again.

Matías.



De: Pharo-users  en nombre de marco 

Enviado: miércoles, 25 de julio de 2018 10:23 a. m.
Para: pharo-users@lists.pharo.org
Asunto: Re: [Pharo-users] OmniBase for Pharo 6

One serious problem left: OmniBaseTest>>testGC fails.

Have a look at the 2 methods

/ODBContainer>>lockDataFile
"Dec, 2010 sas: this code was relying in evaluating a block that was
happening only in win32
but not in *nix. So now I'm making it wait for the lock and then execute
the code normally
because it seems the intention was the same."
| currentSpace defaultSpace |

activeDataFile waitForAddingLock.
currentSpace := activeDataFile == dataFileA ifTrue: [0] ifFalse: [1].
defaultSpace := objectManager defaultObjectSpace.
currentSpace == defaultSpace
ifFalse:
[defaultSpace == 0
ifTrue:
[dataFileA isNil ifTrue: [dataFileA := ODBObjectStorage
openOn: self dataFileNameA].
activeDataFile := dataFileA]
ifFalse:
[dataFileB isNil ifTrue: [dataFileB := ODBObjectStorage
openOn: self dataFileNameB].
activeDataFile := dataFileB].
^self lockDataFile]


ODBFile>>waitForLockAt: pos length: length whileWaitingDo: aBlock
"Wait for lock at given position.
Evaluate aBlock in each iteration."

"Dec, 2010. sas: evaluating code in each iteration while waiting sounds
weird but whatever.
I think this was designed on the wrong assumption that the OS always
will provide a false
in the first try but what actually happens is that in win32 you always
will
get at least one false but in *nixes you don't do see that happening
(which is totally reasonable).
BEWARE of stupid code relying on this stupid assumption (I've already
patched #lockDataFile because of this)."

| startTime currentTime |
(stream lockAt: pos length: length) ifFalse: [
startTime := Time totalSeconds.
[stream lockAt: pos length: length] whileFalse: [
aBlock value.
currentTime := Time totalSeconds.
currentTime - startTime < self timeOutLength
ifFalse: [
ODBLockNotification signal
ifTrue: [startTime := currentTime]
ifFalse: [^ODBCannotLock signal
/

So "sas" did a refactoring in 2010 because he/she thought it is stupid code.
This code change breaks the GarbageCollection of Omnibase.

I reverted the first method to the original code of the Omnibase author,
David Gorisek:

/lockDataFile

| currentSpace defaultSpace |

activeDataFile waitForAddingLockWhileWaitingDo:
[currentSpace := activeDataFile == dataFileA ifTrue: [0] ifFalse: [1].
defaultSpace := objectManager defaultObjectSpace.
currentSpace == defaultSpace
ifFalse:
[defaultSpace == 0
ifTrue:
[dataFileA isNil ifTrue: [dataFileA := ODBObjectStorage
openOn: self dataFileNameA].
activeDataFile := dataFileA]
ifFalse:
[dataFileB isNil ifTrue: [dataFileB := ODBObjectStorage
openOn: self dataFileNameB].
activeDataFile := dataFileB].
^self lockDataFile]]
/
I removed the comment of "sas" from the second method. It is wrong.


The garbage collection works again and the test is green. GC is an important
feature of Omnibase.
It creates a new repository/database file and copies the data into the new
file, compressing the data.
It keeps your database compact and clean. If you don't run it (frequently)
your db files keep on growing...

Matias, your fixes are absolutely valid and should be published - together
with the one above -  in Esteban's repository.




--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
Smalltalk - Pharo Smalltalk Users | Mailing List 
Archive<http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html>
forum.world.st
Pharo Smalltalk Users forum and mailing list archive. Pharo User Forum

Re: [Pharo-users] OmniBase for Pharo 6

2018-07-25 Thread marco

One serious problem left: OmniBaseTest>>testGC fails.

Have a look at the 2 methods

/ODBContainer>>lockDataFile
"Dec, 2010 sas: this code was relying in evaluating a block that was
happening only in win32
but not in *nix. So now I'm making it wait for the lock and then execute
the code normally
because it seems the intention was the same."
| currentSpace defaultSpace |

activeDataFile waitForAddingLock.
currentSpace := activeDataFile == dataFileA ifTrue: [0] ifFalse: [1].
defaultSpace := objectManager defaultObjectSpace.
currentSpace == defaultSpace
ifFalse:
[defaultSpace == 0
ifTrue:
[dataFileA isNil ifTrue: [dataFileA := ODBObjectStorage
openOn: self dataFileNameA].
activeDataFile := dataFileA]
ifFalse:
[dataFileB isNil ifTrue: [dataFileB := ODBObjectStorage
openOn: self dataFileNameB].
activeDataFile := dataFileB].
^self lockDataFile]


ODBFile>>waitForLockAt: pos length: length whileWaitingDo: aBlock
"Wait for lock at given position.
Evaluate aBlock in each iteration."

"Dec, 2010. sas: evaluating code in each iteration while waiting sounds
weird but whatever.
I think this was designed on the wrong assumption that the OS always
will provide a false
in the first try but what actually happens is that in win32 you always
will
get at least one false but in *nixes you don't do see that happening
(which is totally reasonable).
BEWARE of stupid code relying on this stupid assumption (I've already
patched #lockDataFile because of this)."
   
| startTime currentTime |
(stream lockAt: pos length: length) ifFalse: [
startTime := Time totalSeconds.
[stream lockAt: pos length: length] whileFalse: [
aBlock value.
currentTime := Time totalSeconds.
currentTime - startTime < self timeOutLength
ifFalse: [
ODBLockNotification signal
ifTrue: [startTime := currentTime]
ifFalse: [^ODBCannotLock signal
/

So "sas" did a refactoring in 2010 because he/she thought it is stupid code.
This code change breaks the GarbageCollection of Omnibase.

I reverted the first method to the original code of the Omnibase author,
David Gorisek:

/lockDataFile

| currentSpace defaultSpace |

activeDataFile waitForAddingLockWhileWaitingDo:
[currentSpace := activeDataFile == dataFileA ifTrue: [0] ifFalse: [1].
defaultSpace := objectManager defaultObjectSpace.
currentSpace == defaultSpace
ifFalse:
[defaultSpace == 0
ifTrue:
[dataFileA isNil ifTrue: [dataFileA := ODBObjectStorage
openOn: self dataFileNameA].
activeDataFile := dataFileA]
ifFalse:
[dataFileB isNil ifTrue: [dataFileB := ODBObjectStorage
openOn: self dataFileNameB].
activeDataFile := dataFileB].
^self lockDataFile]]
/ 
I removed the comment of "sas" from the second method. It is wrong.


The garbage collection works again and the test is green. GC is an important
feature of Omnibase.
It creates a new repository/database file and copies the data into the new
file, compressing the data.
It keeps your database compact and clean. If you don't run it (frequently)
your db files keep on growing...  

Matias, your fixes are absolutely valid and should be published - together
with the one above -  in Esteban's repository.




--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Re: [Pharo-users] OmniBase for Pharo 6

2018-06-25 Thread PBKResearch

Todd

 

Many thanks for these useful pointers – I had thought of asking you for a hint 
of where problems can occur, but you beat me to it. At present I am just 
playing, to get the feel of what it can do, but when it gets to real data I 
will consider defensive measures – backups and change logs, for example.

 

The application I am considering involves reading and storing quite large 
documents, which are input as XML. Presumably it would be safer to store the 
XML in the database. Similarly, with other complex objects, we could consider a 
hybrid system in which objects are serialized with some other mechanism, e.g. 
STON, and OmniBase is just used to store and manage them. All speculation until 
we try it out.

 

Thanks again

 

Peter Kenny

 

From: Pharo-users  On Behalf Of Todd 
Blanchard
Sent: 25 June 2018 07:31
To: Any question about pharo is welcome 
Subject: Re: [Pharo-users] OmniBase for Pharo 6

 

I will just add that the failures I was experiencing involved storing 
"documents" with deep hierarchies of heterogeneous items.  Something along the 
lines of EMR's (electronic medical records - which if you have any experience 
in that domain - are very complex).

 

The failures would manifest as randomly thrown exceptions while trying to read 
a particularly large and complex hierarchy - which would result in documents 
missing segments when rendered.  Rescuing the data took a couple weeks of 
constantly trying to read smaller chunks and retrying when exceptions were 
thrown.

 

So I would include tests along those lines before trusting it with important 
data.  The database I was working with was quite large when reads began to fail.

 

On Jun 24, 2018, at 3:33 PM, Matias Maretto mailto:mgmare...@hotmail.com> > wrote:

 

Thank you for the info Peter ; I have been working storing and retrieving data 
, everything works fine. I have an ODBPErsistDictionary with almost 20.000 
objects on it, I really get sorprised of how fast can resolve "select:[] 
commands"; I know it is not related with the subjet we are working, but well 

 

 

 


  _  


De: Pharo-users mailto:pharo-users-boun...@lists.pharo.org> > en nombre de PBKResearch 
mailto:pe...@pbkresearch.co.uk> >
Enviado: domingo, 24 de junio de 2018 05:54 p. m.
Para: 'Any question about pharo is welcome'
Asunto: Re: [Pharo-users] OmniBase for Pharo 6

 

Hi Matias (and EstebanLM)

 

I have explained the problem with storing and retrieving Date. Looking through 
the OmniBase code in the repository, I see that there is a whole series of 
extensions for many of the standard classes, which provide methods for 
serializing and deserializing instances of those classes. The extension for 
Date class ignores the start time, and simply saves the day number; the 
retrieval method can only use the days, and so cannot take account of the 
offset for the time zone. If it is necessary to save and restore dates in a way 
which is time-zone sensitive, it will be necessary to modify the code for 
serializing dates to store day and offset. I have not yet worked out how the 
methods are structured, so I have not tried to recode, but all the methods I 
have looked at are only one or two lines, so it should not be difficult.

 

Looking through the classes with extensions, I realise that we may need to 
check rather more examples to be sure that everything is handled correctly. I 
did one little test with String. The standard test in TestEquality just stores 
and retrieves ‘Hello World’. To check that it could handle other encodings, I 
tried the test with a German string encoded in utf8. This worked OK. So thus 
far everything is fine, but it would be a good idea to check correct retrieval 
each time we persist a new class of object.

 

Best wishes

 

Peter Kenny

 

From: Pharo-users mailto:pharo-users-boun...@lists.pharo.org> > On Behalf Of Matias Maretto
Sent: 23 June 2018 19:40
To: Any question about pharo is welcome mailto:pharo-users@lists.pharo.org> >
Subject: Re: [Pharo-users] OmniBase for Pharo 6

 

Hi Peter, thanks for the news. I have been doing some tests, persisting 
diferent kind of objects and until now everythings works fine.

If you find anything else, please let me now.

 

Thanks.

Matias.

 

 


  _  


De: Pharo-users mailto:pharo-users-boun...@lists.pharo.org> > en nombre de PBKResearch 
mailto:pe...@pbkresearch.co.uk> >
Enviado: sábado, 23 de junio de 2018 05:18 p. m.
Para: 'Any question about pharo is welcome'
Asunto: Re: [Pharo-users] OmniBase for Pharo 6

 

Hi Matias

 

A further report. I have worked through the test suite in OmniBaseTests, 
running each test individually. I now have all green except two – testEquality, 
which fails on the storage and retrieval of ‘Date today’, and testGC, which 
fails for reasons I have not yet found.

 

The worrying thing is the apparent change in the instance variables of Date – 
see my exchange with Alistair

Re: [Pharo-users] OmniBase for Pharo 6

2018-06-25 Thread Todd Blanchard

I will just add that the failures I was experiencing involved storing 
"documents" with deep hierarchies of heterogeneous items.  Something along the 
lines of EMR's (electronic medical records - which if you have any experience 
in that domain - are very complex).

The failures would manifest as randomly thrown exceptions while trying to read 
a particularly large and complex hierarchy - which would result in documents 
missing segments when rendered.  Rescuing the data took a couple weeks of 
constantly trying to read smaller chunks and retrying when exceptions were 
thrown.

So I would include tests along those lines before trusting it with important 
data.  The database I was working with was quite large when reads began to fail.

> On Jun 24, 2018, at 3:33 PM, Matias Maretto  wrote:
> 
> Thank you for the info Peter ; I have been working storing and retrieving 
> data , everything works fine. I have an ODBPErsistDictionary with almost 
> 20.000 objects on it, I really get sorprised of how fast can resolve 
> "select:[] commands"; I know it is not related with the subjet we are 
> working, but well 
> 
> 
> 
> 
> De: Pharo-users  <mailto:pharo-users-boun...@lists.pharo.org>> en nombre de PBKResearch 
> mailto:pe...@pbkresearch.co.uk>>
> Enviado: domingo, 24 de junio de 2018 05:54 p. m.
> Para: 'Any question about pharo is welcome'
> Asunto: Re: [Pharo-users] OmniBase for Pharo 6
>  
> Hi Matias (and EstebanLM)
>  
> I have explained the problem with storing and retrieving Date. Looking 
> through the OmniBase code in the repository, I see that there is a whole 
> series of extensions for many of the standard classes, which provide methods 
> for serializing and deserializing instances of those classes. The extension 
> for Date class ignores the start time, and simply saves the day number; the 
> retrieval method can only use the days, and so cannot take account of the 
> offset for the time zone. If it is necessary to save and restore dates in a 
> way which is time-zone sensitive, it will be necessary to modify the code for 
> serializing dates to store day and offset. I have not yet worked out how the 
> methods are structured, so I have not tried to recode, but all the methods I 
> have looked at are only one or two lines, so it should not be difficult.
>  
> Looking through the classes with extensions, I realise that we may need to 
> check rather more examples to be sure that everything is handled correctly. I 
> did one little test with String. The standard test in TestEquality just 
> stores and retrieves ‘Hello World’. To check that it could handle other 
> encodings, I tried the test with a German string encoded in utf8. This worked 
> OK. So thus far everything is fine, but it would be a good idea to check 
> correct retrieval each time we persist a new class of object.
>  
> Best wishes
>  
> Peter Kenny
>  
> From: Pharo-users  <mailto:pharo-users-boun...@lists.pharo.org>> On Behalf Of Matias Maretto
> Sent: 23 June 2018 19:40
> To: Any question about pharo is welcome  <mailto:pharo-users@lists.pharo.org>>
> Subject: Re: [Pharo-users] OmniBase for Pharo 6
>  
> Hi Peter, thanks for the news. I have been doing some tests, persisting 
> diferent kind of objects and until now everythings works fine.
> If you find anything else, please let me now.
>  
> Thanks.
> Matias.
>  
>  
> De: Pharo-users  <mailto:pharo-users-boun...@lists.pharo.org>> en nombre de PBKResearch 
> mailto:pe...@pbkresearch.co.uk>>
> Enviado: sábado, 23 de junio de 2018 05:18 p. m.
> Para: 'Any question about pharo is welcome'
> Asunto: Re: [Pharo-users] OmniBase for Pharo 6
>  
> Hi Matias
>  
> A further report. I have worked through the test suite in OmniBaseTests, 
> running each test individually. I now have all green except two – 
> testEquality, which fails on the storage and retrieval of ‘Date today’, and 
> testGC, which fails for reasons I have not yet found.
>  
> The worrying thing is the apparent change in the instance variables of Date – 
> see my exchange with Alistair Grant in another thread. I shall try to work 
> through the way OmniBase saves and resets the instvars, just in case it might 
> be a general problem.
>  
> I shall let you know of anything else I find.
>  
> Peter Kenny
>  
> From: Pharo-users  <mailto:pharo-users-boun...@lists.pharo.org>> On Behalf Of PBKResearch
> Sent: 23 June 2018 09:18
> To: 'Any question about pharo is welcome'  <mailto:pharo-users@lists.pharo.org>>
> Subject: Re: [Pharo-users] OmniBase for Pharo 6
>  
> Matias
>  
> Thanks. I have made this change, but it does not affect the tests I have run.
>  
> I have focused on

Re: [Pharo-users] OmniBase for Pharo 6

2018-06-24 Thread PBKResearch

Matias

 

Thanks for your report. Since it is working so well for you, I think it is time 
for me to give up working on the test suite and start using it for real. That 
will be for tomorrow (it’s almost midnight here now!).

 

I have realised, by the way, that there is an easy work round for the Date 
problem. If you need to persist a Date with full time-zone consistency, just 
apply ‘start’ to it, which gives a DateAndTime. This will be stored and 
retrieved correctly. When it has been retrieved, just send asDate  to recover 
the correct date.

 

Best wishes

 

Peter Kenny

 

From: Pharo-users  On Behalf Of Matias 
Maretto
Sent: 24 June 2018 23:33
To: Any question about pharo is welcome 
Subject: Re: [Pharo-users] OmniBase for Pharo 6

 

Thank you for the info Peter ; I have been working storing and retrieving data 
, everything works fine. I have an ODBPErsistDictionary with almost 20.000 
objects on it, I really get sorprised of how fast can resolve "select:[] 
commands"; I know it is not related with the subjet we are working, but well  

 

 

 

  _  

De: Pharo-users mailto:pharo-users-boun...@lists.pharo.org> > en nombre de PBKResearch 
mailto:pe...@pbkresearch.co.uk> >
Enviado: domingo, 24 de junio de 2018 05:54 p. m.
Para: 'Any question about pharo is welcome'
Asunto: Re: [Pharo-users] OmniBase for Pharo 6 

 

Hi Matias (and EstebanLM)

 

I have explained the problem with storing and retrieving Date. Looking through 
the OmniBase code in the repository, I see that there is a whole series of 
extensions for many of the standard classes, which provide methods for 
serializing and deserializing instances of those classes. The extension for 
Date class ignores the start time, and simply saves the day number; the 
retrieval method can only use the days, and so cannot take account of the 
offset for the time zone. If it is necessary to save and restore dates in a way 
which is time-zone sensitive, it will be necessary to modify the code for 
serializing dates to store day and offset. I have not yet worked out how the 
methods are structured, so I have not tried to recode, but all the methods I 
have looked at are only one or two lines, so it should not be difficult.

 

Looking through the classes with extensions, I realise that we may need to 
check rather more examples to be sure that everything is handled correctly. I 
did one little test with String. The standard test in TestEquality just stores 
and retrieves ‘Hello World’. To check that it could handle other encodings, I 
tried the test with a German string encoded in utf8. This worked OK. So thus 
far everything is fine, but it would be a good idea to check correct retrieval 
each time we persist a new class of object.

 

Best wishes

 

Peter Kenny

 

From: Pharo-users mailto:pharo-users-boun...@lists.pharo.org> > On Behalf Of Matias Maretto
Sent: 23 June 2018 19:40
To: Any question about pharo is welcome mailto:pharo-users@lists.pharo.org> >
Subject: Re: [Pharo-users] OmniBase for Pharo 6

 

Hi Peter, thanks for the news. I have been doing some tests, persisting 
diferent kind of objects and until now everythings works fine.

If you find anything else, please let me now.

 

Thanks.

Matias.

 

 

  _  

De: Pharo-users mailto:pharo-users-boun...@lists.pharo.org> > en nombre de PBKResearch 
mailto:pe...@pbkresearch.co.uk> >
Enviado: sábado, 23 de junio de 2018 05:18 p. m.
Para: 'Any question about pharo is welcome'
Asunto: Re: [Pharo-users] OmniBase for Pharo 6 

 

Hi Matias

 

A further report. I have worked through the test suite in OmniBaseTests, 
running each test individually. I now have all green except two – testEquality, 
which fails on the storage and retrieval of ‘Date today’, and testGC, which 
fails for reasons I have not yet found.

 

The worrying thing is the apparent change in the instance variables of Date – 
see my exchange with Alistair Grant in another thread. I shall try to work 
through the way OmniBase saves and resets the instvars, just in case it might 
be a general problem.

 

I shall let you know of anything else I find.

 

Peter Kenny

 

From: Pharo-users mailto:pharo-users-boun...@lists.pharo.org> > On Behalf Of PBKResearch
Sent: 23 June 2018 09:18
To: 'Any question about pharo is welcome' mailto:pharo-users@lists.pharo.org> >
Subject: Re: [Pharo-users] OmniBase for Pharo 6

 

Matias

 

Thanks. I have made this change, but it does not affect the tests I have run.

 

I have focused on getting the test suite in OmniBaseTests to run. So far I 
still have 5 greens, 7 reds and one orange. The greens are all the first five 
test methods in the browser list; it seems it half fails on the sixth one 
(TestEquality), hence the orange, and then red for all the rest.

 

One problem is that the test database is created at the start of the test 
suite, and then not removed at the end. This seems to mess up the next attempt 
to run the t

Re: [Pharo-users] OmniBase for Pharo 6

2018-06-24 Thread Matias Maretto

Thank you for the info Peter ; I have been working storing and retrieving data 
, everything works fine. I have an ODBPErsistDictionary with almost 20.000 
objects on it, I really get sorprised of how fast can resolve "select:[] 
commands"; I know it is not related with the subjet we are working, but well 





De: Pharo-users  en nombre de PBKResearch 

Enviado: domingo, 24 de junio de 2018 05:54 p. m.
Para: 'Any question about pharo is welcome'
Asunto: Re: [Pharo-users] OmniBase for Pharo 6


Hi Matias (and EstebanLM)



I have explained the problem with storing and retrieving Date. Looking through 
the OmniBase code in the repository, I see that there is a whole series of 
extensions for many of the standard classes, which provide methods for 
serializing and deserializing instances of those classes. The extension for 
Date class ignores the start time, and simply saves the day number; the 
retrieval method can only use the days, and so cannot take account of the 
offset for the time zone. If it is necessary to save and restore dates in a way 
which is time-zone sensitive, it will be necessary to modify the code for 
serializing dates to store day and offset. I have not yet worked out how the 
methods are structured, so I have not tried to recode, but all the methods I 
have looked at are only one or two lines, so it should not be difficult.



Looking through the classes with extensions, I realise that we may need to 
check rather more examples to be sure that everything is handled correctly. I 
did one little test with String. The standard test in TestEquality just stores 
and retrieves ‘Hello World’. To check that it could handle other encodings, I 
tried the test with a German string encoded in utf8. This worked OK. So thus 
far everything is fine, but it would be a good idea to check correct retrieval 
each time we persist a new class of object.



Best wishes



Peter Kenny



From: Pharo-users  On Behalf Of Matias 
Maretto
Sent: 23 June 2018 19:40
To: Any question about pharo is welcome 
Subject: Re: [Pharo-users] OmniBase for Pharo 6



Hi Peter, thanks for the news. I have been doing some tests, persisting 
diferent kind of objects and until now everythings works fine.

If you find anything else, please let me now.



Thanks.

Matias.







De: Pharo-users 
mailto:pharo-users-boun...@lists.pharo.org>>
 en nombre de PBKResearch 
mailto:pe...@pbkresearch.co.uk>>
Enviado: sábado, 23 de junio de 2018 05:18 p. m.
Para: 'Any question about pharo is welcome'
Asunto: Re: [Pharo-users] OmniBase for Pharo 6



Hi Matias



A further report. I have worked through the test suite in OmniBaseTests, 
running each test individually. I now have all green except two – testEquality, 
which fails on the storage and retrieval of ‘Date today’, and testGC, which 
fails for reasons I have not yet found.



The worrying thing is the apparent change in the instance variables of Date – 
see my exchange with Alistair Grant in another thread. I shall try to work 
through the way OmniBase saves and resets the instvars, just in case it might 
be a general problem.



I shall let you know of anything else I find.



Peter Kenny



From: Pharo-users 
mailto:pharo-users-boun...@lists.pharo.org>>
 On Behalf Of PBKResearch
Sent: 23 June 2018 09:18
To: 'Any question about pharo is welcome' 
mailto:pharo-users@lists.pharo.org>>
Subject: Re: [Pharo-users] OmniBase for Pharo 6



Matias



Thanks. I have made this change, but it does not affect the tests I have run.



I have focused on getting the test suite in OmniBaseTests to run. So far I 
still have 5 greens, 7 reds and one orange. The greens are all the first five 
test methods in the browser list; it seems it half fails on the sixth one 
(TestEquality), hence the orange, and then red for all the rest.



One problem is that the test database is created at the start of the test 
suite, and then not removed at the end. This seems to mess up the next attempt 
to run the tests. I tried to run the OmniBaseTests>>#tearDown manually, but it 
fails, so I have to exit Pharo and delete the test database in Windows.



I intend to continue running the test suite, but I shall run the tests 
individually, and put breakpoints in those that fail. I shall report here if I 
make any progress.



Best wishes



Peter Kenny



From: Pharo-users 
mailto:pharo-users-boun...@lists.pharo.org>>
 On Behalf Of Matias Maretto
Sent: 23 June 2018 01:37
To: Any question about pharo is welcome 
mailto:pharo-users@lists.pharo.org>>
Subject: Re: [Pharo-users] OmniBase for Pharo 6



Peter: I think I found the problem. On ODBFileStream class >> 
accessModeReadOnly the "o" on "only" is not capital. It is  
^#accessModeReadonly  when should be ^#accessModeReadOnly ; so on the 
ODBWin32FileStream >> createOn:  createMode:  accessMode:  shareMode:  
cacheMod

Re: [Pharo-users] OmniBase for Pharo 6

2018-06-24 Thread PBKResearch

Hi Matias (and EstebanLM)

 

I have explained the problem with storing and retrieving Date. Looking
through the OmniBase code in the repository, I see that there is a whole
series of extensions for many of the standard classes, which provide methods
for serializing and deserializing instances of those classes. The extension
for Date class ignores the start time, and simply saves the day number; the
retrieval method can only use the days, and so cannot take account of the
offset for the time zone. If it is necessary to save and restore dates in a
way which is time-zone sensitive, it will be necessary to modify the code
for serializing dates to store day and offset. I have not yet worked out how
the methods are structured, so I have not tried to recode, but all the
methods I have looked at are only one or two lines, so it should not be
difficult.

 

Looking through the classes with extensions, I realise that we may need to
check rather more examples to be sure that everything is handled correctly.
I did one little test with String. The standard test in TestEquality just
stores and retrieves Hello World. To check that it could handle other
encodings, I tried the test with a German string encoded in utf8. This
worked OK. So thus far everything is fine, but it would be a good idea to
check correct retrieval each time we persist a new class of object.

 

Best wishes

 

Peter Kenny

 

From: Pharo-users  On Behalf Of Matias
Maretto
Sent: 23 June 2018 19:40
To: Any question about pharo is welcome 
Subject: Re: [Pharo-users] OmniBase for Pharo 6

 

Hi Peter, thanks for the news. I have been doing some tests, persisting
diferent kind of objects and until now everythings works fine.

If you find anything else, please let me now.

 

Thanks.

Matias.

 

 

  _  

De: Pharo-users mailto:pharo-users-boun...@lists.pharo.org> > en nombre de PBKResearch
mailto:pe...@pbkresearch.co.uk> >
Enviado: sábado, 23 de junio de 2018 05:18 p. m.
Para: 'Any question about pharo is welcome'
Asunto: Re: [Pharo-users] OmniBase for Pharo 6 

 

Hi Matias

 

A further report. I have worked through the test suite in OmniBaseTests,
running each test individually. I now have all green except two 
testEquality, which fails on the storage and retrieval of Date today, and
testGC, which fails for reasons I have not yet found.

 

The worrying thing is the apparent change in the instance variables of Date
 see my exchange with Alistair Grant in another thread. I shall try to work
through the way OmniBase saves and resets the instvars, just in case it
might be a general problem.

 

I shall let you know of anything else I find.

 

Peter Kenny

 

From: Pharo-users mailto:pharo-users-boun...@lists.pharo.org> > On Behalf Of PBKResearch
Sent: 23 June 2018 09:18
To: 'Any question about pharo is welcome' mailto:pharo-users@lists.pharo.org> >
Subject: Re: [Pharo-users] OmniBase for Pharo 6

 

Matias

 

Thanks. I have made this change, but it does not affect the tests I have
run.

 

I have focused on getting the test suite in OmniBaseTests to run. So far I
still have 5 greens, 7 reds and one orange. The greens are all the first
five test methods in the browser list; it seems it half fails on the sixth
one (TestEquality), hence the orange, and then red for all the rest.

 

One problem is that the test database is created at the start of the test
suite, and then not removed at the end. This seems to mess up the next
attempt to run the tests. I tried to run the OmniBaseTests>>#tearDown
manually, but it fails, so I have to exit Pharo and delete the test database
in Windows.

 

I intend to continue running the test suite, but I shall run the tests
individually, and put breakpoints in those that fail. I shall report here if
I make any progress.

 

Best wishes

 

Peter Kenny

 

From: Pharo-users mailto:pharo-users-boun...@lists.pharo.org> > On Behalf Of Matias Maretto
Sent: 23 June 2018 01:37
To: Any question about pharo is welcome mailto:pharo-users@lists.pharo.org> >
Subject: Re: [Pharo-users] OmniBase for Pharo 6

 

Peter: I think I found the problem. On ODBFileStream class >>
accessModeReadOnly the "o" on "only" is not capital. It is
^#accessModeReadonly  when should be ^#accessModeReadOnly ; so on the
ODBWin32FileStream >> createOn:  createMode:  accessMode:  shareMode:
cacheMode:  this part fails:

accessMode = #accessModeReadOnly ifTrue: [acMode := 2147483648
"GENERIC_READ"].

So it cant open the users file for read.  I have fix it and at least for now
I didn't get any "block" error. 

 

 

 

  _  

De: Pharo-users mailto:pharo-users-boun...@lists.pharo.org> > en nombre de PBKResearch
mailto:pe...@pbkresearch.co.uk> >
Enviado: viernes, 22 de junio de 2018 10:39 p. m.
Para: 'Any question about pharo is welcome'
Asunto: Re: [Pharo-users] OmniBase for Pharo 6 

 

Matias

 

Thanks for the hints. I now have 5 greens, b

Re: [Pharo-users] OmniBase for Pharo 6

2018-06-23 Thread Matias Maretto

Hi Peter, thanks for the news. I have been doing some tests, persisting 
diferent kind of objects and until now everythings works fine.

If you find anything else, please let me now.


Thanks.

Matias.




De: Pharo-users  en nombre de PBKResearch 

Enviado: sábado, 23 de junio de 2018 05:18 p. m.
Para: 'Any question about pharo is welcome'
Asunto: Re: [Pharo-users] OmniBase for Pharo 6


Hi Matias



A further report. I have worked through the test suite in OmniBaseTests, 
running each test individually. I now have all green except two – testEquality, 
which fails on the storage and retrieval of ‘Date today’, and testGC, which 
fails for reasons I have not yet found.



The worrying thing is the apparent change in the instance variables of Date – 
see my exchange with Alistair Grant in another thread. I shall try to work 
through the way OmniBase saves and resets the instvars, just in case it might 
be a general problem.



I shall let you know of anything else I find.



Peter Kenny



From: Pharo-users  On Behalf Of PBKResearch
Sent: 23 June 2018 09:18
To: 'Any question about pharo is welcome' 
Subject: Re: [Pharo-users] OmniBase for Pharo 6



Matias



Thanks. I have made this change, but it does not affect the tests I have run.



I have focused on getting the test suite in OmniBaseTests to run. So far I 
still have 5 greens, 7 reds and one orange. The greens are all the first five 
test methods in the browser list; it seems it half fails on the sixth one 
(TestEquality), hence the orange, and then red for all the rest.



One problem is that the test database is created at the start of the test 
suite, and then not removed at the end. This seems to mess up the next attempt 
to run the tests. I tried to run the OmniBaseTests>>#tearDown manually, but it 
fails, so I have to exit Pharo and delete the test database in Windows.



I intend to continue running the test suite, but I shall run the tests 
individually, and put breakpoints in those that fail. I shall report here if I 
make any progress.



Best wishes



Peter Kenny



From: Pharo-users 
mailto:pharo-users-boun...@lists.pharo.org>>
 On Behalf Of Matias Maretto
Sent: 23 June 2018 01:37
To: Any question about pharo is welcome 
mailto:pharo-users@lists.pharo.org>>
Subject: Re: [Pharo-users] OmniBase for Pharo 6



Peter: I think I found the problem. On ODBFileStream class >> 
accessModeReadOnly the "o" on "only" is not capital. It is  
^#accessModeReadonly  when should be ^#accessModeReadOnly ; so on the 
ODBWin32FileStream >> createOn:  createMode:  accessMode:  shareMode:  
cacheMode:  this part fails:

accessMode = #accessModeReadOnly ifTrue: [acMode := 2147483648 "GENERIC_READ"].

So it cant open the users file for read.  I have fix it and at least for now I 
didn't get any "block" error.









De: Pharo-users 
mailto:pharo-users-boun...@lists.pharo.org>>
 en nombre de PBKResearch 
mailto:pe...@pbkresearch.co.uk>>
Enviado: viernes, 22 de junio de 2018 10:39 p. m.
Para: 'Any question about pharo is welcome'
Asunto: Re: [Pharo-users] OmniBase for Pharo 6



Matias



Thanks for the hints. I now have 5 greens, but all the rest are red. I am still 
getting the ‘File cannot be locked’ message. Are you doing better than that? I 
may try a few trials using it for real, rather than the test suite.



Thanks again



Peter Kenny



From: Pharo-users 
mailto:pharo-users-boun...@lists.pharo.org>>
 On Behalf Of Matias Maretto
Sent: 22 June 2018 22:54
To: Any question about pharo is welcome 
mailto:pharo-users@lists.pharo.org>>
Subject: Re: [Pharo-users] OmniBase for Pharo 6



Hi Peter, yes I had the same error at the beginning. I have done 2 minor  
changes. Now it seems to be working fine (Although I am still running more 
tests). Here:



ODBWin32FileStream >>

closeHandle: aHandle

"Close an open Win32 object handle, freeing any resources held by it.

Once closed a handle is no longer valid. Answer whether the function

succeeds.

See Win32 SDK help for more information.



BOOL CloseHandle(

HANDLE  hObject

// handle of object to close

);"



""

^ self ffiCall: #(ulong CloseHandle(long aHandle))







ODBWin32FileStream >>

lockFile: aHandle offsetLow: loPos offsetHigh: hiPos lengthLow: loLength 
lengthHigh: hiLength

""



^ self

ffiCall: #(long LockFile #(long aHandle , ulong loPos , ulong hiPos , ulong 
loLength , ulong hiLength))









De: Pharo-users 
mailto:pharo-users-boun...@lists.pharo.org>>
 en nombre de PBKResearch 
mailto:pe...@pbkresearch.co.uk>>
Enviado: viernes, 22 de junio de 2018 09:45 p. m.
Para: 'Any question about pharo is welcome'
Asunto: Re: [Pharo-users] OmniBase for Pharo 6



Matias



I have just loaded Esteban’s package in a new Pharo 6.1 under Windows 10. I get 
an err

Re: [Pharo-users] OmniBase for Pharo 6

2018-06-23 Thread PBKResearch

Hi Matias

 

A further report. I have worked through the test suite in OmniBaseTests,
running each test individually. I now have all green except two -
testEquality, which fails on the storage and retrieval of 'Date today', and
testGC, which fails for reasons I have not yet found.

 

The worrying thing is the apparent change in the instance variables of Date
- see my exchange with Alistair Grant in another thread. I shall try to work
through the way OmniBase saves and resets the instvars, just in case it
might be a general problem.

 

I shall let you know of anything else I find.

 

Peter Kenny

 

From: Pharo-users  On Behalf Of
PBKResearch
Sent: 23 June 2018 09:18
To: 'Any question about pharo is welcome' 
Subject: Re: [Pharo-users] OmniBase for Pharo 6

 

Matias

 

Thanks. I have made this change, but it does not affect the tests I have
run.

 

I have focused on getting the test suite in OmniBaseTests to run. So far I
still have 5 greens, 7 reds and one orange. The greens are all the first
five test methods in the browser list; it seems it half fails on the sixth
one (TestEquality), hence the orange, and then red for all the rest.

 

One problem is that the test database is created at the start of the test
suite, and then not removed at the end. This seems to mess up the next
attempt to run the tests. I tried to run the OmniBaseTests>>#tearDown
manually, but it fails, so I have to exit Pharo and delete the test database
in Windows.

 

I intend to continue running the test suite, but I shall run the tests
individually, and put breakpoints in those that fail. I shall report here if
I make any progress.

 

Best wishes

 

Peter Kenny

 

From: Pharo-users mailto:pharo-users-boun...@lists.pharo.org> > On Behalf Of Matias Maretto
Sent: 23 June 2018 01:37
To: Any question about pharo is welcome mailto:pharo-users@lists.pharo.org> >
Subject: Re: [Pharo-users] OmniBase for Pharo 6

 

Peter: I think I found the problem. On ODBFileStream class >>
accessModeReadOnly the "o" on "only" is not capital. It is
^#accessModeReadonly  when should be ^#accessModeReadOnly ; so on the
ODBWin32FileStream >> createOn:  createMode:  accessMode:  shareMode:
cacheMode:  this part fails:

accessMode = #accessModeReadOnly ifTrue: [acMode := 2147483648
"GENERIC_READ"].

So it cant open the users file for read.  I have fix it and at least for now
I didn't get any "block" error. 

 

 

 

  _  

De: Pharo-users mailto:pharo-users-boun...@lists.pharo.org> > en nombre de PBKResearch
mailto:pe...@pbkresearch.co.uk> >
Enviado: viernes, 22 de junio de 2018 10:39 p. m.
Para: 'Any question about pharo is welcome'
Asunto: Re: [Pharo-users] OmniBase for Pharo 6 

 

Matias

 

Thanks for the hints. I now have 5 greens, but all the rest are red. I am
still getting the 'File cannot be locked' message. Are you doing better than
that? I may try a few trials using it for real, rather than the test suite.

 

Thanks again

 

Peter Kenny

 

From: Pharo-users mailto:pharo-users-boun...@lists.pharo.org> > On Behalf Of Matias Maretto
Sent: 22 June 2018 22:54
To: Any question about pharo is welcome mailto:pharo-users@lists.pharo.org> >
Subject: Re: [Pharo-users] OmniBase for Pharo 6

 

Hi Peter, yes I had the same error at the beginning. I have done 2 minor
changes. Now it seems to be working fine (Although I am still running more
tests). Here: 

 

ODBWin32FileStream >> 

closeHandle: aHandle

"Close an open Win32 object handle, freeing any resources held by it.

Once closed a handle is no longer valid. Answer whether the function

succeeds.

See Win32 SDK help for more information.

 

BOOL CloseHandle(

HANDLE  hObject 

// handle of object to close  

);"

 

""

^ self ffiCall: #(ulong CloseHandle(long aHandle))

 

 

 

ODBWin32FileStream >> 

lockFile: aHandle offsetLow: loPos offsetHigh: hiPos lengthLow: loLength
lengthHigh: hiLength

""

 

^ self

ffiCall: #(long LockFile #(long aHandle , ulong loPos , ulong hiPos , ulong
loLength , ulong hiLength))

 

 

 

  _  

De: Pharo-users mailto:pharo-users-boun...@lists.pharo.org> > en nombre de PBKResearch
mailto:pe...@pbkresearch.co.uk> >
Enviado: viernes, 22 de junio de 2018 09:45 p. m.
Para: 'Any question about pharo is welcome'
Asunto: Re: [Pharo-users] OmniBase for Pharo 6 

 

Matias

 

I have just loaded Esteban's package in a new Pharo 6.1 under Windows 10. I
get an error message saying 'File cannot be locked. Try again?'. When I
select 'no', all tests are run and give red. Are you still running on win 7?
If so, I must be doing something wrong. Can you give more details of the FFI
corrections you made, please?

 

Many thanks

 

Peter Kenny

 

From: Pharo-users mailto:pharo-users-boun...@lists.pharo.org> > On Behalf Of Matias Maretto
Sent: 22 June 2018 21:07
To: Any question about pharo is welcome mailto:pharo

Re: [Pharo-users] OmniBase for Pharo 6

2018-06-23 Thread PBKResearch

Matias

 

Thanks. I have made this change, but it does not affect the tests I have
run.

 

I have focused on getting the test suite in OmniBaseTests to run. So far I
still have 5 greens, 7 reds and one orange. The greens are all the first
five test methods in the browser list; it seems it half fails on the sixth
one (TestEquality), hence the orange, and then red for all the rest.

 

One problem is that the test database is created at the start of the test
suite, and then not removed at the end. This seems to mess up the next
attempt to run the tests. I tried to run the OmniBaseTests>>#tearDown
manually, but it fails, so I have to exit Pharo and delete the test database
in Windows.

 

I intend to continue running the test suite, but I shall run the tests
individually, and put breakpoints in those that fail. I shall report here if
I make any progress.

 

Best wishes

 

Peter Kenny

 

From: Pharo-users  On Behalf Of Matias
Maretto
Sent: 23 June 2018 01:37
To: Any question about pharo is welcome 
Subject: Re: [Pharo-users] OmniBase for Pharo 6

 

Peter: I think I found the problem. On ODBFileStream class >>
accessModeReadOnly the "o" on "only" is not capital. It is
^#accessModeReadonly  when should be ^#accessModeReadOnly ; so on the
ODBWin32FileStream >> createOn:  createMode:  accessMode:  shareMode:
cacheMode:  this part fails:

accessMode = #accessModeReadOnly ifTrue: [acMode := 2147483648
"GENERIC_READ"].

So it cant open the users file for read.  I have fix it and at least for now
I didn't get any "block" error. 

 

 

 

  _  

De: Pharo-users mailto:pharo-users-boun...@lists.pharo.org> > en nombre de PBKResearch
mailto:pe...@pbkresearch.co.uk> >
Enviado: viernes, 22 de junio de 2018 10:39 p. m.
Para: 'Any question about pharo is welcome'
Asunto: Re: [Pharo-users] OmniBase for Pharo 6 

 

Matias

 

Thanks for the hints. I now have 5 greens, but all the rest are red. I am
still getting the 'File cannot be locked' message. Are you doing better than
that? I may try a few trials using it for real, rather than the test suite.

 

Thanks again

 

Peter Kenny

 

From: Pharo-users mailto:pharo-users-boun...@lists.pharo.org> > On Behalf Of Matias Maretto
Sent: 22 June 2018 22:54
To: Any question about pharo is welcome mailto:pharo-users@lists.pharo.org> >
Subject: Re: [Pharo-users] OmniBase for Pharo 6

 

Hi Peter, yes I had the same error at the beginning. I have done 2 minor
changes. Now it seems to be working fine (Although I am still running more
tests). Here: 

 

ODBWin32FileStream >> 

closeHandle: aHandle

"Close an open Win32 object handle, freeing any resources held by it.

Once closed a handle is no longer valid. Answer whether the function

succeeds.

See Win32 SDK help for more information.

 

BOOL CloseHandle(

HANDLE  hObject 

// handle of object to close  

);"

 

""

^ self ffiCall: #(ulong CloseHandle(long aHandle))

 

 

 

ODBWin32FileStream >> 

lockFile: aHandle offsetLow: loPos offsetHigh: hiPos lengthLow: loLength
lengthHigh: hiLength

""

 

^ self

ffiCall: #(long LockFile #(long aHandle , ulong loPos , ulong hiPos , ulong
loLength , ulong hiLength))

 

 

 

  _  

De: Pharo-users mailto:pharo-users-boun...@lists.pharo.org> > en nombre de PBKResearch
mailto:pe...@pbkresearch.co.uk> >
Enviado: viernes, 22 de junio de 2018 09:45 p. m.
Para: 'Any question about pharo is welcome'
Asunto: Re: [Pharo-users] OmniBase for Pharo 6 

 

Matias

 

I have just loaded Esteban's package in a new Pharo 6.1 under Windows 10. I
get an error message saying 'File cannot be locked. Try again?'. When I
select 'no', all tests are run and give red. Are you still running on win 7?
If so, I must be doing something wrong. Can you give more details of the FFI
corrections you made, please?

 

Many thanks

 

Peter Kenny

 

From: Pharo-users mailto:pharo-users-boun...@lists.pharo.org> > On Behalf Of Matias Maretto
Sent: 22 June 2018 21:07
To: Any question about pharo is welcome mailto:pharo-users@lists.pharo.org> >
Subject: Re: [Pharo-users] OmniBase for Pharo 6

 

Esteban: it's working fine, I had to made a minor corrections on 2 FFI calls
and now everithing seems to be working fine.

For What I saw with Voyage-UnqLite only String Objects can be used to
searilize; Omnibase allow to persist almost any kind of objects, thats the
part I like about it. 

 

 

 

  _  

De: Pharo-users mailto:pharo-users-boun...@lists.pharo.org> > en nombre de Esteban
Lorenzano mailto:esteba...@gmail.com> >
Enviado: jueves, 21 de junio de 2018 08:19 p. m.
Para: Any question about pharo is welcome
Asunto: Re: [Pharo-users] OmniBase for Pharo 6 

 

I did it manually and I took like 5 min :P
but this was really easy, just a bunch of FFI calls.

Esteban

> On 21 Jun 2018, at 15:31, Sean P. DeNigris mailto:s...@clipperadams.com> > w

Re: [Pharo-users] OmniBase for Pharo 6

2018-06-22 Thread Matias Maretto

Peter: I think I found the problem. On ODBFileStream class >> 
accessModeReadOnly the "o" on "only" is not capital. It is  
^#accessModeReadonly  when should be ^#accessModeReadOnly ; so on the 
ODBWin32FileStream >> createOn:  createMode:  accessMode:  shareMode:  
cacheMode:  this part fails:

accessMode = #accessModeReadOnly ifTrue: [acMode := 2147483648 "GENERIC_READ"].
So it cant open the users file for read.  I have fix it and at least for now I 
didn't get any "block" error.

De: Pharo-users  en nombre de PBKResearch 

Enviado: viernes, 22 de junio de 2018 10:39 p. m.
Para: 'Any question about pharo is welcome'
Asunto: Re: [Pharo-users] OmniBase for Pharo 6

Matias

Thanks for the hints. I now have 5 greens, but all the rest are red. I am still 
getting the ‘File cannot be locked’ message. Are you doing better than that? I 
may try a few trials using it for real, rather than the test suite.

Thanks again

Peter Kenny

From: Pharo-users  On Behalf Of Matias 
Maretto
Sent: 22 June 2018 22:54
To: Any question about pharo is welcome 
Subject: Re: [Pharo-users] OmniBase for Pharo 6

Hi Peter, yes I had the same error at the beginning. I have done 2 minor  
changes. Now it seems to be working fine (Although I am still running more 
tests). Here:

ODBWin32FileStream >>

closeHandle: aHandle

"Close an open Win32 object handle, freeing any resources held by it.

Once closed a handle is no longer valid. Answer whether the function

succeeds.

See Win32 SDK help for more information.

BOOL CloseHandle(

HANDLE  hObject

// handle of object to close

);"

""

^ self ffiCall: #(ulong CloseHandle(long aHandle))

ODBWin32FileStream >>

lockFile: aHandle offsetLow: loPos offsetHigh: hiPos lengthLow: loLength 
lengthHigh: hiLength

""

^ self

ffiCall: #(long LockFile #(long aHandle , ulong loPos , ulong hiPos , ulong 
loLength , ulong hiLength))

De: Pharo-users 
mailto:pharo-users-boun...@lists.pharo.org>>
 en nombre de PBKResearch 
mailto:pe...@pbkresearch.co.uk>>
Enviado: viernes, 22 de junio de 2018 09:45 p. m.
Para: 'Any question about pharo is welcome'
Asunto: Re: [Pharo-users] OmniBase for Pharo 6

Matias

I have just loaded Esteban’s package in a new Pharo 6.1 under Windows 10. I get 
an error message saying ‘File cannot be locked. Try again?’. When I select 
‘no’, all tests are run and give red. Are you still running on win 7? If so, I 
must be doing something wrong. Can you give more details of the FFI corrections 
you made, please?

Many thanks

Peter Kenny

From: Pharo-users 
mailto:pharo-users-boun...@lists.pharo.org>>
 On Behalf Of Matias Maretto
Sent: 22 June 2018 21:07
To: Any question about pharo is welcome 
mailto:pharo-users@lists.pharo.org>>
Subject: Re: [Pharo-users] OmniBase for Pharo 6

Esteban: it's working fine, I had to made a minor corrections on 2 FFI calls 
and now everithing seems to be working fine.

For What I saw with Voyage-UnqLite only String Objects can be used to 
searilize; Omnibase allow to persist almost any kind of objects, thats the part 
I like about it.

De: Pharo-users 
mailto:pharo-users-boun...@lists.pharo.org>>
 en nombre de Esteban Lorenzano 
mailto:esteba...@gmail.com>>
Enviado: jueves, 21 de junio de 2018 08:19 p. m.
Para: Any question about pharo is welcome
Asunto: Re: [Pharo-users] OmniBase for Pharo 6

I did it manually and I took like 5 min :P
but this was really easy, just a bunch of FFI calls.

Esteban

> On 21 Jun 2018, at 15:31, Sean P. DeNigris 
> mailto:s...@clipperadams.com>> wrote:
>
> EstebanLM wrote
>> I just made a “blind port”… migrated the old FFI to new UFFI
>
> Did you do this manually or use some migration tool? How long did it take?
>
>
>
> -
> Cheers,
> Sean
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Smalltalk - Pharo Smalltalk Users | Mailing List 
Archive<http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html>

forum.world.st

Pharo Smalltalk Users forum and mailing list archive. Pharo User Forum

>

Re: [Pharo-users] OmniBase for Pharo 6

2018-06-22 Thread Matias Maretto

Peter: when I run code like this example:

db := OmniBase createOn: 'C:\temp\testOmni'.
aTrans := db newTransaction.

aTrans root at: 'Hello' put: (OrderedCollection with: 1 with: 2 with: 3).
aTrans commit.
db close.

db := OmniBase openOn: 'C:\temp\testOmni'.
aTrans := db newTransaction.
(aTrans root at: 'Hello') size

Everything is fine, but sometimes when I close an reopen the base I get the 
"lock" error, but even when I get the error the base is still opened and 
transactions run fine. I will take a closer look to the lockFIle method.

I will tell you if I find a solution. (I am using Win 7).

De: Pharo-users  en nombre de PBKResearch 

Enviado: viernes, 22 de junio de 2018 10:39 p. m.
Para: 'Any question about pharo is welcome'
Asunto: Re: [Pharo-users] OmniBase for Pharo 6

Matias

Thanks for the hints. I now have 5 greens, but all the rest are red. I am still 
getting the ‘File cannot be locked’ message. Are you doing better than that? I 
may try a few trials using it for real, rather than the test suite.

Thanks again

Peter Kenny

From: Pharo-users  On Behalf Of Matias 
Maretto
Sent: 22 June 2018 22:54
To: Any question about pharo is welcome 
Subject: Re: [Pharo-users] OmniBase for Pharo 6

Hi Peter, yes I had the same error at the beginning. I have done 2 minor  
changes. Now it seems to be working fine (Although I am still running more 
tests). Here:

ODBWin32FileStream >>

closeHandle: aHandle

"Close an open Win32 object handle, freeing any resources held by it.

Once closed a handle is no longer valid. Answer whether the function

succeeds.

See Win32 SDK help for more information.

BOOL CloseHandle(

HANDLE  hObject

// handle of object to close

);"

""

^ self ffiCall: #(ulong CloseHandle(long aHandle))

ODBWin32FileStream >>

lockFile: aHandle offsetLow: loPos offsetHigh: hiPos lengthLow: loLength 
lengthHigh: hiLength

""

^ self

ffiCall: #(long LockFile #(long aHandle , ulong loPos , ulong hiPos , ulong 
loLength , ulong hiLength))

De: Pharo-users 
mailto:pharo-users-boun...@lists.pharo.org>>
 en nombre de PBKResearch 
mailto:pe...@pbkresearch.co.uk>>
Enviado: viernes, 22 de junio de 2018 09:45 p. m.
Para: 'Any question about pharo is welcome'
Asunto: Re: [Pharo-users] OmniBase for Pharo 6

Matias

I have just loaded Esteban’s package in a new Pharo 6.1 under Windows 10. I get 
an error message saying ‘File cannot be locked. Try again?’. When I select 
‘no’, all tests are run and give red. Are you still running on win 7? If so, I 
must be doing something wrong. Can you give more details of the FFI corrections 
you made, please?

Many thanks

Peter Kenny

From: Pharo-users 
mailto:pharo-users-boun...@lists.pharo.org>>
 On Behalf Of Matias Maretto
Sent: 22 June 2018 21:07
To: Any question about pharo is welcome 
mailto:pharo-users@lists.pharo.org>>
Subject: Re: [Pharo-users] OmniBase for Pharo 6

Esteban: it's working fine, I had to made a minor corrections on 2 FFI calls 
and now everithing seems to be working fine.

For What I saw with Voyage-UnqLite only String Objects can be used to 
searilize; Omnibase allow to persist almost any kind of objects, thats the part 
I like about it.

De: Pharo-users 
mailto:pharo-users-boun...@lists.pharo.org>>
 en nombre de Esteban Lorenzano 
mailto:esteba...@gmail.com>>
Enviado: jueves, 21 de junio de 2018 08:19 p. m.
Para: Any question about pharo is welcome
Asunto: Re: [Pharo-users] OmniBase for Pharo 6

I did it manually and I took like 5 min :P
but this was really easy, just a bunch of FFI calls.

Esteban

> On 21 Jun 2018, at 15:31, Sean P. DeNigris 
> mailto:s...@clipperadams.com>> wrote:
>
> EstebanLM wrote
>> I just made a “blind port”… migrated the old FFI to new UFFI
>
> Did you do this manually or use some migration tool? How long did it take?
>
>
>
> -
> Cheers,
> Sean
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Smalltalk - Pharo Smalltalk Users | Mailing List 
Archive<http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html>

forum.world.st

Pharo Smalltalk Users forum and mailing list archive. Pharo User Forum

>

Re: [Pharo-users] OmniBase for Pharo 6

2018-06-22 Thread PBKResearch

Matias

Thanks for the hints. I now have 5 greens, but all the rest are red. I am
still getting the 'File cannot be locked' message. Are you doing better than
that? I may try a few trials using it for real, rather than the test suite.

Thanks again

Peter Kenny

From: Pharo-users  On Behalf Of Matias
Maretto
Sent: 22 June 2018 22:54
To: Any question about pharo is welcome 
Subject: Re: [Pharo-users] OmniBase for Pharo 6

Hi Peter, yes I had the same error at the beginning. I have done 2 minor
changes. Now it seems to be working fine (Although I am still running more
tests). Here: 

ODBWin32FileStream >> 

closeHandle: aHandle

"Close an open Win32 object handle, freeing any resources held by it.

Once closed a handle is no longer valid. Answer whether the function

succeeds.

See Win32 SDK help for more information.

BOOL CloseHandle(

HANDLE  hObject 

// handle of object to close  

);"

""

^ self ffiCall: #(ulong CloseHandle(long aHandle))

ODBWin32FileStream >> 

lockFile: aHandle offsetLow: loPos offsetHigh: hiPos lengthLow: loLength
lengthHigh: hiLength

""

^ self

ffiCall: #(long LockFile #(long aHandle , ulong loPos , ulong hiPos , ulong
loLength , ulong hiLength))

  _  

De: Pharo-users mailto:pharo-users-boun...@lists.pharo.org> > en nombre de PBKResearch
mailto:pe...@pbkresearch.co.uk> >
Enviado: viernes, 22 de junio de 2018 09:45 p. m.
Para: 'Any question about pharo is welcome'
Asunto: Re: [Pharo-users] OmniBase for Pharo 6 

Matias

I have just loaded Esteban's package in a new Pharo 6.1 under Windows 10. I
get an error message saying 'File cannot be locked. Try again?'. When I
select 'no', all tests are run and give red. Are you still running on win 7?
If so, I must be doing something wrong. Can you give more details of the FFI
corrections you made, please?

Many thanks

Peter Kenny

From: Pharo-users mailto:pharo-users-boun...@lists.pharo.org> > On Behalf Of Matias Maretto
Sent: 22 June 2018 21:07
To: Any question about pharo is welcome mailto:pharo-users@lists.pharo.org> >
Subject: Re: [Pharo-users] OmniBase for Pharo 6

Esteban: it's working fine, I had to made a minor corrections on 2 FFI calls
and now everithing seems to be working fine.

For What I saw with Voyage-UnqLite only String Objects can be used to
searilize; Omnibase allow to persist almost any kind of objects, thats the
part I like about it. 

  _  

De: Pharo-users mailto:pharo-users-boun...@lists.pharo.org> > en nombre de Esteban
Lorenzano mailto:esteba...@gmail.com> >
Enviado: jueves, 21 de junio de 2018 08:19 p. m.
Para: Any question about pharo is welcome
Asunto: Re: [Pharo-users] OmniBase for Pharo 6 

I did it manually and I took like 5 min :P
but this was really easy, just a bunch of FFI calls.

Esteban

> On 21 Jun 2018, at 15:31, Sean P. DeNigris mailto:s...@clipperadams.com> > wrote:
> 
> EstebanLM wrote
>> I just made a "blind port". migrated the old FFI to new UFFI
> 
> Did you do this manually or use some migration tool? How long did it take?
> 
> 
> 
> -
> Cheers,
> Sean
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html 

 <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> Smalltalk -
Pharo Smalltalk Users | Mailing List Archive

forum.world.st

Pharo Smalltalk Users forum and mailing list archive. Pharo User Forum

>

Re: [Pharo-users] OmniBase for Pharo 6

2018-06-22 Thread Matias Maretto

Hi Peter, yes I had the same error at the beginning. I have done 2 minor  
changes. Now it seems to be working fine (Although I am still running more 
tests). Here:

ODBWin32FileStream >>

closeHandle: aHandle
"Close an open Win32 object handle, freeing any resources held by it.
Once closed a handle is no longer valid. Answer whether the function
succeeds. See Win32 SDK help for more information.

BOOL CloseHandle(
HANDLE  hObject // handle of object to close
);"

""
^ self ffiCall: #(ulong CloseHandle(long aHandle))

ODBWin32FileStream >>

lockFile: aHandle offsetLow: loPos offsetHigh: hiPos lengthLow: loLength 
lengthHigh: hiLength

""

^ self
ffiCall: #(long LockFile #(long aHandle , ulong loPos , ulong hiPos , ulong 
loLength , ulong hiLength))

De: Pharo-users  en nombre de PBKResearch 

Enviado: viernes, 22 de junio de 2018 09:45 p. m.
Para: 'Any question about pharo is welcome'
Asunto: Re: [Pharo-users] OmniBase for Pharo 6

Matias

I have just loaded Esteban’s package in a new Pharo 6.1 under Windows 10. I get 
an error message saying ‘File cannot be locked. Try again?’. When I select 
‘no’, all tests are run and give red. Are you still running on win 7? If so, I 
must be doing something wrong. Can you give more details of the FFI corrections 
you made, please?

Many thanks

Peter Kenny

From: Pharo-users  On Behalf Of Matias 
Maretto
Sent: 22 June 2018 21:07
To: Any question about pharo is welcome 
Subject: Re: [Pharo-users] OmniBase for Pharo 6

Esteban: it's working fine, I had to made a minor corrections on 2 FFI calls 
and now everithing seems to be working fine.

For What I saw with Voyage-UnqLite only String Objects can be used to 
searilize; Omnibase allow to persist almost any kind of objects, thats the part 
I like about it.

De: Pharo-users 
mailto:pharo-users-boun...@lists.pharo.org>>
 en nombre de Esteban Lorenzano 
mailto:esteba...@gmail.com>>
Enviado: jueves, 21 de junio de 2018 08:19 p. m.
Para: Any question about pharo is welcome
Asunto: Re: [Pharo-users] OmniBase for Pharo 6

I did it manually and I took like 5 min :P
but this was really easy, just a bunch of FFI calls.

Esteban

> On 21 Jun 2018, at 15:31, Sean P. DeNigris 
> mailto:s...@clipperadams.com>> wrote:
>
> EstebanLM wrote
>> I just made a “blind port”… migrated the old FFI to new UFFI
>
> Did you do this manually or use some migration tool? How long did it take?
>
>
>
> -
> Cheers,
> Sean
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Smalltalk - Pharo Smalltalk Users | Mailing List 
Archive<http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html>

forum.world.st

Pharo Smalltalk Users forum and mailing list archive. Pharo User Forum

>

Re: [Pharo-users] OmniBase for Pharo 6

2018-06-22 Thread PBKResearch

Matias

I have just loaded Esteban's package in a new Pharo 6.1 under Windows 10. I
get an error message saying 'File cannot be locked. Try again?'. When I
select 'no', all tests are run and give red. Are you still running on win 7?
If so, I must be doing something wrong. Can you give more details of the FFI
corrections you made, please?

Many thanks

Peter Kenny

From: Pharo-users  On Behalf Of Matias
Maretto
Sent: 22 June 2018 21:07
To: Any question about pharo is welcome 
Subject: Re: [Pharo-users] OmniBase for Pharo 6

Esteban: it's working fine, I had to made a minor corrections on 2 FFI calls
and now everithing seems to be working fine.

For What I saw with Voyage-UnqLite only String Objects can be used to
searilize; Omnibase allow to persist almost any kind of objects, thats the
part I like about it. 

  _  

De: Pharo-users mailto:pharo-users-boun...@lists.pharo.org> > en nombre de Esteban
Lorenzano mailto:esteba...@gmail.com> >
Enviado: jueves, 21 de junio de 2018 08:19 p. m.
Para: Any question about pharo is welcome
Asunto: Re: [Pharo-users] OmniBase for Pharo 6 

I did it manually and I took like 5 min :P
but this was really easy, just a bunch of FFI calls.

Esteban

> On 21 Jun 2018, at 15:31, Sean P. DeNigris mailto:s...@clipperadams.com> > wrote:
> 
> EstebanLM wrote
>> I just made a "blind port". migrated the old FFI to new UFFI
> 
> Did you do this manually or use some migration tool? How long did it take?
> 
> 
> 
> -
> Cheers,
> Sean
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html 

 <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> Smalltalk -
Pharo Smalltalk Users | Mailing List Archive

forum.world.st

Pharo Smalltalk Users forum and mailing list archive. Pharo User Forum

>

Re: [Pharo-users] OmniBase for Pharo 6

2018-06-22 Thread Matias Maretto

Esteban: it's working fine, I had to made a minor corrections on 2 FFI calls 
and now everithing seems to be working fine.

For What I saw with Voyage-UnqLite only String Objects can be used to 
searilize; Omnibase allow to persist almost any kind of objects, thats the part 
I like about it.

De: Pharo-users  en nombre de Esteban 
Lorenzano 
Enviado: jueves, 21 de junio de 2018 08:19 p. m.
Para: Any question about pharo is welcome
Asunto: Re: [Pharo-users] OmniBase for Pharo 6

I did it manually and I took like 5 min :P
but this was really easy, just a bunch of FFI calls.

Esteban

> On 21 Jun 2018, at 15:31, Sean P. DeNigris  wrote:
>
> EstebanLM wrote
>> I just made a “blind port”… migrated the old FFI to new UFFI
>
> Did you do this manually or use some migration tool? How long did it take?
>
>
>
> -
> Cheers,
> Sean
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
Smalltalk - Pharo Smalltalk Users | Mailing List 
Archive<http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html>
forum.world.st
Pharo Smalltalk Users forum and mailing list archive. Pharo User Forum

>

Re: [Pharo-users] OmniBase for Pharo 6

2018-06-21 Thread Esteban Lorenzano

I did it manually and I took like 5 min :P
but this was really easy, just a bunch of FFI calls.

Esteban

> On 21 Jun 2018, at 15:31, Sean P. DeNigris  wrote:
> 
> EstebanLM wrote
>> I just made a “blind port”… migrated the old FFI to new UFFI
> 
> Did you do this manually or use some migration tool? How long did it take?
> 
> 
> 
> -
> Cheers,
> Sean
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
>

Re: [Pharo-users] OmniBase for Pharo 6

2018-06-21 Thread Sean P. DeNigris

EstebanLM wrote
> I just made a “blind port”… migrated the old FFI to new UFFI

Did you do this manually or use some migration tool? How long did it take?



-
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Re: [Pharo-users] OmniBase for Pharo 6

2018-06-21 Thread Esteban Lorenzano

ok, I just updated it (and split tests from main package). 
now it loads and tests pass except for 3 failures. 

I let you provide a PR to fix them if that’s an issue :)

cheers, 
Esteban

> On 21 Jun 2018, at 13:49, Esteban Lorenzano  wrote:
> 
> btw… the baseline I created will just load OmniBase. Some dependencies (like 
> OSProcess) where not included (as I said, I just made it loadable in P6+, 
> some work may be needed to make it pass).
> 
> cheers,
> Esteban
> 
>> On 21 Jun 2018, at 13:13, Matias Maretto > <mailto:mgmare...@hotmail.com>> wrote:
>> 
>> Hi, Thank you Esteban, I will load it and run some test; very thankful. Todd 
>> , Tim, also thank you for your comments, I will certainly take a look a 
>> Voyage.
>> I will let you know how it turns out.
>> 
>> Matias.
>> 
>> 
>> 
>> De: Pharo-users > <mailto:pharo-users-boun...@lists.pharo.org>> en nombre de Esteban Lorenzano 
>> mailto:esteba...@gmail.com>>
>> Enviado: jueves, 21 de junio de 2018 07:10 a. m.
>> Para: Any question about pharo is welcome
>> Asunto: Re: [Pharo-users] OmniBase for Pharo 6
>>  
>> Hi, 
>> 
>> I just made a “blind port” of OmniBase to Pharo6+ (migrated the old FFI to 
>> new UFFI).
>> New port is here: 
>> 
>> https://github.com/estebanlm/OmniBase <https://github.com/estebanlm/OmniBase>
>>  <https://github.com/estebanlm/OmniBase> 
>> estebanlm/OmniBase <https://github.com/estebanlm/OmniBase>
>> github.com <http://github.com/>
>> OmniBase is Smalltalk efficient objects repository, BTree and filesystem 
>> based with full ACID features
>> 
>> 
>> and can be load like this: 
>> 
>> Metacello new 
>> repository: 'github://estebanlm/OmniBase/src 
>> ';
>> baseline: 'OmniBase';
>> load.
>> 
>> PLEASE note I’ve never used OmniBase and I don’t know if this port will work 
>> out of the box. But if it was working, it should continue working now (and 
>> this list can help to get you rolling). 
>> 
>> cheers, 
>> Esteban
>> 
>> ps: I always wanted to do a Voyage-OmniBase… maybe this is the moment? :P
>> 
>> 
>> 
>>> On 21 Jun 2018, at 08:13, Tim Mackinnon >> <mailto:tim@testit.works>> wrote:
>>> 
>>> I too used it in Dolphin and it was fine, But i don’t think it gets used 
>>> much in Pharo and so has probably decayed, isn’t Voyage an object dB or 
>>> Gemstone?
>>> 
>>> (Todd & everyone, a gentle reminder to try and leave personality opinions 
>>> at the door , we’ve already had another thread that got overly heated 
>>> unnecessarily. Our community is small and we need to avoid knife fights. 
>>> The technical stuff is already hard enough)
>>> 
>>> Tim
>>> 
>>> Sent from my iPhone
>>> 
>>> On 21 Jun 2018, at 00:20, Matias Maretto >> <mailto:mgmare...@hotmail.com>> wrote:
>>> 
>>>>  thanks for your answer Todd. I know omnibase from dolphin. Now I am 
>>>> starting a new Project and I want to use pharo. Would you recommend me 
>>>> another object database?
>>>> Thanks.
>>>> 
>>>> El 20 jun. 2018 19:29, Todd Blanchard >>> <mailto:tblanch...@mac.com>> escribió:
>>>> FWIW, I have used it before and I don't have anything good to say about 
>>>> the library or the individual who wrote it.
>>>> 
>>>> I'd look for something else.
>>>> 
>>>> On Jun 20, 2018, at 3:05 PM, pablo digonzelli Argentina 
>>>> mailto:pdigonze...@gmail.com>> wrote:
>>>> 
>>>> Hi try this. I do not know if working on pharo 6 or 7
>>>> 
>>>> https://github.com/sebastianconcept/OmniBase 
>>>> <https://github.com/sebastianconcept/OmniBase>
>>>> 
>>>> 
>>>> 
>>>> El mié., 20 jun. 2018 a las 17:22, Matias Maretto (>>> <mailto:mgmare...@hotmail.com>>) escribió:
>>>> Hi folks, does anyone know how to get OmniBase for Pharo 6?.  The Package 
>>>> on Pharo.org <http://pharo.org/> is for pharo 4, I tried to install them 
>>>> manually from the MCZ files, but I get a strange error in a closeHandle 
>>>> method.  ulong 'CloseHandle' (long) 
>>>> module:'kernel32.dll'>
>>>> ^self externalCallFailed. 
>>>> I am using win 7.
>>>> Thanks.
>>>> Matias.
>>>> 
>>>> 
>>>> 
>>>> 
>>>> -- 
>>>> Ing. Pablo Digonzelli 
>>>> Software Solutions
>>>> IP-Solutiones SRL
>>>> 25 de Mayo 521
>>>> Email: pdigonze...@softsargentina.com 
>>>> <mailto:pdigonze...@softsargentina.com>
>>>> pdigonze...@gmail.com <mailto:pdigonze...@gmail.com>
>>>> Cel: 543815982714
>>>> 
>>>> 
>> 
>> 
>

Re: [Pharo-users] OmniBase for Pharo 6

2018-06-21 Thread Esteban Lorenzano

btw… the baseline I created will just load OmniBase. Some dependencies (like 
OSProcess) where not included (as I said, I just made it loadable in P6+, some 
work may be needed to make it pass).

cheers,
Esteban

> On 21 Jun 2018, at 13:13, Matias Maretto  wrote:
> 
> Hi, Thank you Esteban, I will load it and run some test; very thankful. Todd 
> , Tim, also thank you for your comments, I will certainly take a look a 
> Voyage.
> I will let you know how it turns out.
> 
> Matias.
> 
> 
> 
> De: Pharo-users  <mailto:pharo-users-boun...@lists.pharo.org>> en nombre de Esteban Lorenzano 
> mailto:esteba...@gmail.com>>
> Enviado: jueves, 21 de junio de 2018 07:10 a. m.
> Para: Any question about pharo is welcome
> Asunto: Re: [Pharo-users] OmniBase for Pharo 6
>  
> Hi, 
> 
> I just made a “blind port” of OmniBase to Pharo6+ (migrated the old FFI to 
> new UFFI).
> New port is here: 
> 
> https://github.com/estebanlm/OmniBase <https://github.com/estebanlm/OmniBase>
>  <https://github.com/estebanlm/OmniBase>  
> estebanlm/OmniBase <https://github.com/estebanlm/OmniBase>
> github.com <http://github.com/>
> OmniBase is Smalltalk efficient objects repository, BTree and filesystem 
> based with full ACID features
> 
> 
> and can be load like this: 
> 
> Metacello new 
> repository: 'github://estebanlm/OmniBase/src 
> ';
> baseline: 'OmniBase';
> load.
> 
> PLEASE note I’ve never used OmniBase and I don’t know if this port will work 
> out of the box. But if it was working, it should continue working now (and 
> this list can help to get you rolling). 
> 
> cheers, 
> Esteban
> 
> ps: I always wanted to do a Voyage-OmniBase… maybe this is the moment? :P
> 
> 
> 
>> On 21 Jun 2018, at 08:13, Tim Mackinnon > <mailto:tim@testit.works>> wrote:
>> 
>> I too used it in Dolphin and it was fine, But i don’t think it gets used 
>> much in Pharo and so has probably decayed, isn’t Voyage an object dB or 
>> Gemstone?
>> 
>> (Todd & everyone, a gentle reminder to try and leave personality opinions at 
>> the door , we’ve already had another thread that got overly heated 
>> unnecessarily. Our community is small and we need to avoid knife fights. The 
>> technical stuff is already hard enough)
>> 
>> Tim
>> 
>> Sent from my iPhone
>> 
>> On 21 Jun 2018, at 00:20, Matias Maretto > <mailto:mgmare...@hotmail.com>> wrote:
>> 
>>>  thanks for your answer Todd. I know omnibase from dolphin. Now I am 
>>> starting a new Project and I want to use pharo. Would you recommend me 
>>> another object database?
>>> Thanks.
>>> 
>>> El 20 jun. 2018 19:29, Todd Blanchard >> <mailto:tblanch...@mac.com>> escribió:
>>> FWIW, I have used it before and I don't have anything good to say about the 
>>> library or the individual who wrote it.
>>> 
>>> I'd look for something else.
>>> 
>>> On Jun 20, 2018, at 3:05 PM, pablo digonzelli Argentina 
>>> mailto:pdigonze...@gmail.com>> wrote:
>>> 
>>> Hi try this. I do not know if working on pharo 6 or 7
>>> 
>>> https://github.com/sebastianconcept/OmniBase 
>>> <https://github.com/sebastianconcept/OmniBase>
>>> 
>>> 
>>> 
>>> El mié., 20 jun. 2018 a las 17:22, Matias Maretto (>> <mailto:mgmare...@hotmail.com>>) escribió:
>>> Hi folks, does anyone know how to get OmniBase for Pharo 6?.  The Package 
>>> on Pharo.org <http://pharo.org/> is for pharo 4, I tried to install them 
>>> manually from the MCZ files, but I get a strange error in a closeHandle 
>>> method.  ulong 'CloseHandle' (long) 
>>> module:'kernel32.dll'>
>>> ^self externalCallFailed. 
>>> I am using win 7.
>>> Thanks.
>>> Matias.
>>> 
>>> 
>>> 
>>> 
>>> -- 
>>> Ing. Pablo Digonzelli 
>>> Software Solutions
>>> IP-Solutiones SRL
>>> 25 de Mayo 521
>>> Email: pdigonze...@softsargentina.com 
>>> <mailto:pdigonze...@softsargentina.com>
>>> pdigonze...@gmail.com <mailto:pdigonze...@gmail.com>
>>> Cel: 543815982714
>>> 
>>> 
> 
>

Re: [Pharo-users] OmniBase for Pharo 6

2018-06-21 Thread Matias Maretto

Hi, Thank you Esteban, I will load it and run some test; very thankful. Todd ,
Tim, also thank you for your comments, I will certainly take a look a Voyage.
I will let you know how it turns out.

Matias.

De: Pharo-users en nombre de Esteban
Lorenzano
Enviado: jueves, 21 de junio de 2018 07:10 a. m.
Para: Any question about pharo is welcome
Asunto: Re: [Pharo-users] OmniBase for Pharo 6

Hi,

I just made a “blind port” of OmniBase to Pharo6+ (migrated the old FFI to new
UFFI).
New port is here:

https://github.com/estebanlm/OmniBase
[https://avatars0.githubusercontent.com/u/513630?s=400=4]<https://github.com/estebanlm/OmniBase>

estebanlm/OmniBase<https://github.com/estebanlm/OmniBase>
github.com
OmniBase is Smalltalk efficient objects repository, BTree and filesystem based
with full ACID features

and can be load like this:

Metacello new
repository: 'github://estebanlm/OmniBase/src';
baseline: 'OmniBase';
load.

PLEASE note I’ve never used OmniBase and I don’t know if this port will work
out of the box. But if it was working, it should continue working now (and this
list can help to get you rolling).

cheers,
Esteban

ps: I always wanted to do a Voyage-OmniBase… maybe this is the moment? :P

On 21 Jun 2018, at 08:13, Tim Mackinnon
mailto:tim@testit.works>> wrote:

I too used it in Dolphin and it was fine, But i don’t think it gets used much
in Pharo and so has probably decayed, isn’t Voyage an object dB or Gemstone?

(Todd & everyone, a gentle reminder to try and leave personality opinions at
the door , we’ve already had another thread that got overly heated
unnecessarily. Our community is small and we need to avoid knife fights. The
technical stuff is already hard enough)

Tim

Sent from my iPhone

On 21 Jun 2018, at 00:20, Matias Maretto
mailto:mgmare...@hotmail.com>> wrote:

thanks for your answer Todd. I know omnibase from dolphin. Now I am starting a
new Project and I want to use pharo. Would you recommend me another object
database?
Thanks.

El 20 jun. 2018 19:29, Todd Blanchard
mailto:tblanch...@mac.com>> escribió:
FWIW, I have used it before and I don't have anything good to say about the
library or the individual who wrote it.

I'd look for something else.

On Jun 20, 2018, at 3:05 PM, pablo digonzelli Argentina
mailto:pdigonze...@gmail.com>> wrote:

Hi try this. I do not know if working on pharo 6 or 7

https://github.com/sebastianconcept/OmniBase

El mié., 20 jun. 2018 a las 17:22, Matias Maretto
(mailto:mgmare...@hotmail.com>>) escribió:

Hi folks, does anyone know how to get OmniBase for Pharo 6?. The Package on
Pharo.org<http://pharo.org/> is for pharo 4, I tried to install them manually
from the MCZ files, but I get a strange error in a closeHandle method.
ulong 'CloseHandle' (long)
module:'kernel32.dll'>
^self externalCallFailed.
I am using win 7.
Thanks.
Matias.

--
Ing. Pablo Digonzelli
Software Solutions
IP-Solutiones SRL
25 de Mayo 521
Email: pdigonze...@softsargentina.com<mailto:pdigonze...@softsargentina.com>
pdigonze...@gmail.com<mailto:pdigonze...@gmail.com>
Cel: 543815982714

Re: [Pharo-users] OmniBase for Pharo 6

2018-06-21 Thread Tim Mackinnon

Todd - thanks for clarifying - thats a fairer non-emotive assessment. I also 
know that you often helpfully chip in here too, so thanks for that too.

Tim

> On 21 Jun 2018, at 11:18, Todd Blanchard  wrote:
> 
> I'll just leave it with production data was lost through creeping file 
> corruption and recovery services were paid for but not rendered.  If you need 
> your data to be safe, I'd pick something else.
> 
> Sorry if that seems offensive, that's my experience with it.
> 
>> On Jun 20, 2018, at 11:13 PM, Tim Mackinnon > > wrote:
>> 
>> I too used it in Dolphin and it was fine, But i don’t think it gets used 
>> much in Pharo and so has probably decayed, isn’t Voyage an object dB or 
>> Gemstone?
>> 
>> (Todd & everyone, a gentle reminder to try and leave personality opinions at 
>> the door , we’ve already had another thread that got overly heated 
>> unnecessarily. Our community is small and we need to avoid knife fights. The 
>> technical stuff is already hard enough)
>> 
>> Tim
>> 
>> Sent from my iPhone
>> 
>> On 21 Jun 2018, at 00:20, Matias Maretto > > wrote:
>> 
>>>  thanks for your answer Todd. I know omnibase from dolphin. Now I am 
>>> starting a new Project and I want to use pharo. Would you recommend me 
>>> another object database?
>>> Thanks.
>>> 
>>> El 20 jun. 2018 19:29, Todd Blanchard >> > escribió:
>>> FWIW, I have used it before and I don't have anything good to say about the 
>>> library or the individual who wrote it.
>>> 
>>> I'd look for something else.
>>> 
>>> On Jun 20, 2018, at 3:05 PM, pablo digonzelli Argentina 
>>> mailto:pdigonze...@gmail.com>> wrote:
>>> 
>>> Hi try this. I do not know if working on pharo 6 or 7
>>> 
>>> https://github.com/sebastianconcept/OmniBase 
>>> 
>>> 
>>> 
>>> 
>>> El mié., 20 jun. 2018 a las 17:22, Matias Maretto (>> >) escribió:
>>> Hi folks, does anyone know how to get OmniBase for Pharo 6?.  The Package 
>>> on Pharo.org  is for pharo 4, I tried to install them 
>>> manually from the MCZ files, but I get a strange error in a closeHandle 
>>> method.  ulong 'CloseHandle' (long) 
>>> module:'kernel32.dll'>
>>> ^self externalCallFailed. 
>>> I am using win 7.
>>> Thanks.
>>> Matias.
>>> 
>>> 
>>> 
>>> 
>>> -- 
>>> Ing. Pablo Digonzelli 
>>> Software Solutions
>>> IP-Solutiones SRL
>>> 25 de Mayo 521
>>> Email: pdigonze...@softsargentina.com 
>>> 
>>> pdigonze...@gmail.com 
>>> Cel: 543815982714
>>> 
>>> 
>

Re: [Pharo-users] OmniBase for Pharo 6

2018-06-21 Thread Todd Blanchard

I'll just leave it with production data was lost through creeping file 
corruption and recovery services were paid for but not rendered.  If you need 
your data to be safe, I'd pick something else.

Sorry if that seems offensive, that's my experience with it.

> On Jun 20, 2018, at 11:13 PM, Tim Mackinnon  wrote:
> 
> I too used it in Dolphin and it was fine, But i don’t think it gets used much 
> in Pharo and so has probably decayed, isn’t Voyage an object dB or Gemstone?
> 
> (Todd & everyone, a gentle reminder to try and leave personality opinions at 
> the door , we’ve already had another thread that got overly heated 
> unnecessarily. Our community is small and we need to avoid knife fights. The 
> technical stuff is already hard enough)
> 
> Tim
> 
> Sent from my iPhone
> 
> On 21 Jun 2018, at 00:20, Matias Maretto  > wrote:
> 
>>  thanks for your answer Todd. I know omnibase from dolphin. Now I am 
>> starting a new Project and I want to use pharo. Would you recommend me 
>> another object database?
>> Thanks.
>> 
>> El 20 jun. 2018 19:29, Todd Blanchard > > escribió:
>> FWIW, I have used it before and I don't have anything good to say about the 
>> library or the individual who wrote it.
>> 
>> I'd look for something else.
>> 
>> On Jun 20, 2018, at 3:05 PM, pablo digonzelli Argentina 
>> mailto:pdigonze...@gmail.com>> wrote:
>> 
>> Hi try this. I do not know if working on pharo 6 or 7
>> 
>> https://github.com/sebastianconcept/OmniBase 
>> 
>> 
>> 
>> 
>> El mié., 20 jun. 2018 a las 17:22, Matias Maretto (> >) escribió:
>> Hi folks, does anyone know how to get OmniBase for Pharo 6?.  The Package on 
>> Pharo.org  is for pharo 4, I tried to install them 
>> manually from the MCZ files, but I get a strange error in a closeHandle 
>> method.  ulong 'CloseHandle' (long) 
>> module:'kernel32.dll'>
>> ^self externalCallFailed. 
>> I am using win 7.
>> Thanks.
>> Matias.
>> 
>> 
>> 
>> 
>> -- 
>> Ing. Pablo Digonzelli 
>> Software Solutions
>> IP-Solutiones SRL
>> 25 de Mayo 521
>> Email: pdigonze...@softsargentina.com 
>> pdigonze...@gmail.com 
>> Cel: 543815982714
>> 
>>

Re: [Pharo-users] OmniBase for Pharo 6

2018-06-21 Thread Esteban Lorenzano

btw… a viable alternative to omnibase if your needs are not more than 1TB is 
Voyage-Unqlite. 

Is the closest we have to a real object database running.

(now, I need to check why it is not working properly on windows, but that’s 
another 2c)

Esteban

> On 21 Jun 2018, at 09:10, Esteban Lorenzano  wrote:
> 
> Hi, 
> 
> I just made a “blind port” of OmniBase to Pharo6+ (migrated the old FFI to 
> new UFFI).
> New port is here: 
> 
> https://github.com/estebanlm/OmniBase 
> 
> and can be load like this: 
> 
> Metacello new 
>   repository: 'github://estebanlm/OmniBase/src 
> ';
>   baseline: 'OmniBase';
>   load.
> 
> PLEASE note I’ve never used OmniBase and I don’t know if this port will work 
> out of the box. But if it was working, it should continue working now (and 
> this list can help to get you rolling). 
> 
> cheers, 
> Esteban
> 
> ps: I always wanted to do a Voyage-OmniBase… maybe this is the moment? :P
> 
> 
> 
>> On 21 Jun 2018, at 08:13, Tim Mackinnon > > wrote:
>> 
>> I too used it in Dolphin and it was fine, But i don’t think it gets used 
>> much in Pharo and so has probably decayed, isn’t Voyage an object dB or 
>> Gemstone?
>> 
>> (Todd & everyone, a gentle reminder to try and leave personality opinions at 
>> the door , we’ve already had another thread that got overly heated 
>> unnecessarily. Our community is small and we need to avoid knife fights. The 
>> technical stuff is already hard enough)
>> 
>> Tim
>> 
>> Sent from my iPhone
>> 
>> On 21 Jun 2018, at 00:20, Matias Maretto > > wrote:
>> 
>>>  thanks for your answer Todd. I know omnibase from dolphin. Now I am 
>>> starting a new Project and I want to use pharo. Would you recommend me 
>>> another object database?
>>> Thanks.
>>> 
>>> El 20 jun. 2018 19:29, Todd Blanchard >> > escribió:
>>> FWIW, I have used it before and I don't have anything good to say about the 
>>> library or the individual who wrote it.
>>> 
>>> I'd look for something else.
>>> 
>>> On Jun 20, 2018, at 3:05 PM, pablo digonzelli Argentina 
>>> mailto:pdigonze...@gmail.com>> wrote:
>>> 
>>> Hi try this. I do not know if working on pharo 6 or 7
>>> 
>>> https://github.com/sebastianconcept/OmniBase 
>>> 
>>> 
>>> 
>>> 
>>> El mié., 20 jun. 2018 a las 17:22, Matias Maretto (>> >) escribió:
>>> Hi folks, does anyone know how to get OmniBase for Pharo 6?.  The Package 
>>> on Pharo.org  is for pharo 4, I tried to install them 
>>> manually from the MCZ files, but I get a strange error in a closeHandle 
>>> method.  ulong 'CloseHandle' (long) 
>>> module:'kernel32.dll'>
>>> ^self externalCallFailed. 
>>> I am using win 7.
>>> Thanks.
>>> Matias.
>>> 
>>> 
>>> 
>>> 
>>> -- 
>>> Ing. Pablo Digonzelli 
>>> Software Solutions
>>> IP-Solutiones SRL
>>> 25 de Mayo 521
>>> Email: pdigonze...@softsargentina.com 
>>> 
>>> pdigonze...@gmail.com 
>>> Cel: 543815982714
>>> 
>>> 
>

Re: [Pharo-users] OmniBase for Pharo 6

2018-06-21 Thread Esteban Lorenzano

Hi, 

I just made a “blind port” of OmniBase to Pharo6+ (migrated the old FFI to new 
UFFI).
New port is here: 

https://github.com/estebanlm/OmniBase 

and can be load like this: 

Metacello new 
repository: 'github://estebanlm/OmniBase/src';
baseline: 'OmniBase';
load.

PLEASE note I’ve never used OmniBase and I don’t know if this port will work 
out of the box. But if it was working, it should continue working now (and this 
list can help to get you rolling). 

cheers, 
Esteban

ps: I always wanted to do a Voyage-OmniBase… maybe this is the moment? :P



> On 21 Jun 2018, at 08:13, Tim Mackinnon  wrote:
> 
> I too used it in Dolphin and it was fine, But i don’t think it gets used much 
> in Pharo and so has probably decayed, isn’t Voyage an object dB or Gemstone?
> 
> (Todd & everyone, a gentle reminder to try and leave personality opinions at 
> the door , we’ve already had another thread that got overly heated 
> unnecessarily. Our community is small and we need to avoid knife fights. The 
> technical stuff is already hard enough)
> 
> Tim
> 
> Sent from my iPhone
> 
> On 21 Jun 2018, at 00:20, Matias Maretto  > wrote:
> 
>>  thanks for your answer Todd. I know omnibase from dolphin. Now I am 
>> starting a new Project and I want to use pharo. Would you recommend me 
>> another object database?
>> Thanks.
>> 
>> El 20 jun. 2018 19:29, Todd Blanchard > > escribió:
>> FWIW, I have used it before and I don't have anything good to say about the 
>> library or the individual who wrote it.
>> 
>> I'd look for something else.
>> 
>> On Jun 20, 2018, at 3:05 PM, pablo digonzelli Argentina 
>> mailto:pdigonze...@gmail.com>> wrote:
>> 
>> Hi try this. I do not know if working on pharo 6 or 7
>> 
>> https://github.com/sebastianconcept/OmniBase 
>> 
>> 
>> 
>> 
>> El mié., 20 jun. 2018 a las 17:22, Matias Maretto (> >) escribió:
>> Hi folks, does anyone know how to get OmniBase for Pharo 6?.  The Package on 
>> Pharo.org  is for pharo 4, I tried to install them 
>> manually from the MCZ files, but I get a strange error in a closeHandle 
>> method.  ulong 'CloseHandle' (long) 
>> module:'kernel32.dll'>
>> ^self externalCallFailed. 
>> I am using win 7.
>> Thanks.
>> Matias.
>> 
>> 
>> 
>> 
>> -- 
>> Ing. Pablo Digonzelli 
>> Software Solutions
>> IP-Solutiones SRL
>> 25 de Mayo 521
>> Email: pdigonze...@softsargentina.com 
>> pdigonze...@gmail.com 
>> Cel: 543815982714
>> 
>>

Re: [Pharo-users] OmniBase for Pharo 6

2018-06-21 Thread Tim Mackinnon

I too used it in Dolphin and it was fine, But i don’t think it gets used much 
in Pharo and so has probably decayed, isn’t Voyage an object dB or Gemstone?

(Todd & everyone, a gentle reminder to try and leave personality opinions at 
the door , we’ve already had another thread that got overly heated 
unnecessarily. Our community is small and we need to avoid knife fights. The 
technical stuff is already hard enough)

Tim

Sent from my iPhone

> On 21 Jun 2018, at 00:20, Matias Maretto  wrote:
> 
>  thanks for your answer Todd. I know omnibase from dolphin. Now I am starting 
> a new Project and I want to use pharo. Would you recommend me another object 
> database?
> Thanks.
> 
> El 20 jun. 2018 19:29, Todd Blanchard  escribió:
> FWIW, I have used it before and I don't have anything good to say about the 
> library or the individual who wrote it.
> 
> I'd look for something else.
> 
> On Jun 20, 2018, at 3:05 PM, pablo digonzelli Argentina 
>  wrote:
> 
> Hi try this. I do not know if working on pharo 6 or 7
> 
> https://github.com/sebastianconcept/OmniBase
> 
> 
> 
> El mié., 20 jun. 2018 a las 17:22, Matias Maretto () 
> escribió:
> Hi folks, does anyone know how to get OmniBase for Pharo 6?.  The Package on 
> Pharo.org is for pharo 4, I tried to install them manually from the MCZ 
> files, but I get a strange error in a closeHandle method.  constant expected -> ulong 'CloseHandle' (long) module:'kernel32.dll'>
> ^self externalCallFailed. 
> I am using win 7.
> Thanks.
> Matias.
> 
> 
> 
> 
> -- 
> Ing. Pablo Digonzelli 
> Software Solutions
> IP-Solutiones SRL
> 25 de Mayo 521
> Email: pdigonze...@softsargentina.com
> pdigonze...@gmail.com
> Cel: 543815982714
> 
>

Re: [Pharo-users] OmniBase for Pharo 6

2018-06-20 Thread Matias Maretto

 thanks for your answer Todd. I know omnibase from dolphin. Now I am starting a 
new Project and I want to use pharo. Would you recommend me another object 
database?
Thanks.

El 20 jun. 2018 19:29, Todd Blanchard  escribió:
FWIW, I have used it before and I don't have anything good to say about the 
library or the individual who wrote it.

I'd look for something else.

On Jun 20, 2018, at 3:05 PM, pablo digonzelli Argentina 
mailto:pdigonze...@gmail.com>> wrote:

Hi try this. I do not know if working on pharo 6 or 7

https://github.com/sebastianconcept/OmniBase



El mié., 20 jun. 2018 a las 17:22, Matias Maretto 
(mailto:mgmare...@hotmail.com>>) escribió:

Hi folks, does anyone know how to get OmniBase for Pharo 6?.  The Package on 
Pharo.org is for pharo 4, I tried to install them manually 
from the MCZ files, but I get a strange error in a closeHandle method. 
 ulong 'CloseHandle' (long) 
module:'kernel32.dll'>
^self externalCallFailed.
I am using win 7.
Thanks.
Matias.




--
Ing. Pablo Digonzelli
Software Solutions
IP-Solutiones SRL
25 de Mayo 521
Email: pdigonze...@softsargentina.com
pdigonze...@gmail.com
Cel: 543815982714

Re: [Pharo-users] OmniBase for Pharo 6

2018-06-20 Thread Matias Maretto

Hi pablo, Thanks for your answer, yes I tried it, doesn't work. When load the 
package omnibase-base I Get the same error.


El 20 jun. 2018 19:05, pablo digonzelli Argentina  
escribió:
Hi try this. I do not know if working on pharo 6 or 7

https://github.com/sebastianconcept/OmniBase



El mié., 20 jun. 2018 a las 17:22, Matias Maretto 
(mailto:mgmare...@hotmail.com>>) escribió:

Hi folks, does anyone know how to get OmniBase for Pharo 6?.  The Package on 
Pharo.org is for pharo 4, I tried to install them manually from the MCZ files, 
but I get a strange error in a closeHandle method.  ulong 'CloseHandle' (long) module:'kernel32.dll'>
^self externalCallFailed.
I am using win 7.
Thanks.
Matias.



--
Ing. Pablo Digonzelli
Software Solutions
IP-Solutiones SRL
25 de Mayo 521
Email: pdigonze...@softsargentina.com
pdigonze...@gmail.com
Cel: 543815982714

Re: [Pharo-users] OmniBase for Pharo 6

2018-06-20 Thread Todd Blanchard

FWIW, I have used it before and I don't have anything good to say about the 
library or the individual who wrote it.

I'd look for something else.

> On Jun 20, 2018, at 3:05 PM, pablo digonzelli Argentina 
>  wrote:
> 
> Hi try this. I do not know if working on pharo 6 or 7
> 
> https://github.com/sebastianconcept/OmniBase 
> 
> 
> 
> 
> El mié., 20 jun. 2018 a las 17:22, Matias Maretto ( >) escribió:
> Hi folks, does anyone know how to get OmniBase for Pharo 6?.  The Package on 
> Pharo.org is for pharo 4, I tried to install them manually from the MCZ 
> files, but I get a strange error in a closeHandle method.  constant expected -> ulong 'CloseHandle' (long) module:'kernel32.dll'>
> ^self externalCallFailed. 
> I am using win 7.
> Thanks.
> Matias.
> 
> 
> 
> 
> -- 
> Ing. Pablo Digonzelli 
> Software Solutions
> IP-Solutiones SRL
> 25 de Mayo 521
> Email: pdigonze...@softsargentina.com 
> pdigonze...@gmail.com 
> Cel: 543815982714

Re: [Pharo-users] OmniBase for Pharo 6

2018-06-20 Thread pablo digonzelli Argentina

Hi try this. I do not know if working on pharo 6 or 7

https://github.com/sebastianconcept/OmniBase



El mié., 20 jun. 2018 a las 17:22, Matias Maretto ()
escribió:

> Hi folks, does anyone know how to get OmniBase for Pharo 6?.  The Package
> on Pharo.org is for pharo 4, I tried to install them manually from the MCZ
> files, but I get a strange error in a closeHandle method.  constant expected -> ulong 'CloseHandle' (long) module:'kernel32.dll'>
> ^self externalCallFailed.
> I am using win 7.
> Thanks.
> Matias.
>
>

-- 
*Ing. Pablo Digonzelli *
Software Solutions
IP-Solutiones SRL
25 de Mayo 521
Email: pdigonze...@softsargentina.com
pdigonze...@gmail.com
Cel: 543815982714

Re: [Pharo-users] OmniBase for Pharo 6

Re: [Pharo-users] OmniBase for Pharo 6

Re: [Pharo-users] OmniBase for Pharo 6

Re: [Pharo-users] OmniBase for Pharo 6

Re: [Pharo-users] OmniBase for Pharo 6

Re: [Pharo-users] OmniBase for Pharo 6

Re: [Pharo-users] OmniBase for Pharo 6

Re: [Pharo-users] OmniBase for Pharo 6

Re: [Pharo-users] OmniBase for Pharo 6

Re: [Pharo-users] OmniBase for Pharo 6

Re: [Pharo-users] OmniBase for Pharo 6

Re: [Pharo-users] OmniBase for Pharo 6

Re: [Pharo-users] OmniBase for Pharo 6

Re: [Pharo-users] OmniBase for Pharo 6

Re: [Pharo-users] OmniBase for Pharo 6

Re: [Pharo-users] OmniBase for Pharo 6

Re: [Pharo-users] OmniBase for Pharo 6

Re: [Pharo-users] OmniBase for Pharo 6

Re: [Pharo-users] OmniBase for Pharo 6

Re: [Pharo-users] OmniBase for Pharo 6

Re: [Pharo-users] OmniBase for Pharo 6

Re: [Pharo-users] OmniBase for Pharo 6

Re: [Pharo-users] OmniBase for Pharo 6

Re: [Pharo-users] OmniBase for Pharo 6

Re: [Pharo-users] OmniBase for Pharo 6

Re: [Pharo-users] OmniBase for Pharo 6

Re: [Pharo-users] OmniBase for Pharo 6

Re: [Pharo-users] OmniBase for Pharo 6

Re: [Pharo-users] OmniBase for Pharo 6

Re: [Pharo-users] OmniBase for Pharo 6

Re: [Pharo-users] OmniBase for Pharo 6

Re: [Pharo-users] OmniBase for Pharo 6

Re: [Pharo-users] OmniBase for Pharo 6

33 matches

Site Navigation

Mail list logo

Footer information