Hi Todd,
we want to do some more testing before merging it into the upstream
repository.
-- Pavel
čt 21. 11. 2019 v 14:34 odesílatel Todd Blanchard via Pharo-users <
pharo-users@lists.pharo.org> napsal:
> Hi Pavel,
>
> I've just gotten around to figuring out BaslineOf and packages. I see
> thi
--- Begin Message ---
Hi Pavel,
I've just gotten around to figuring out BaslineOf and packages. I see this
work is in a branch on your own repository.
Do you plan to do a pull request back to the original repository? I feel like
we have database code all over the place and no clear "official"
The error you hit was because the package loader was smart enough to notice
that there was a version conflict between the version of a subproject
already in the image and what the new load instructions were telling it to
load. The title of the debugger you pasted in alludes to that fact.
So wha
--- Begin Message ---
Nice! Thanks.
So here is maybe a stupid question (and I'm gonna read the wiki stuff on
packages next) but it seems to me that the package loader should notice that
glorp is already loaded and not load it if glorp is specified as a prerequisite
but instead it fails.
Is th
Hi Todd,
El sáb., 19 oct. 2019 a las 13:11, Todd Blanchard via Pharo-users (<
pharo-users@lists.pharo.org>) escribió:
> I should probably mention that I do not really have a great handle on how
> package configurations work these days.
>
> Coming back to Smalltalk after a long time away.
>
>
Welc
On Sat, Oct 19, 2019 at 01:26:10AM -0700, Todd Blanchard via Pharo-users wrote:
> I loaded GLORP+P3 without issue.
> Trying to load SQLite3 - it also wants to load GLORP which complains of
> conflict.
Todd, to load SQLite3 only:
Metacello new
repository: 'github://astares/Pharo-UDBC/src';
--- Begin Message ---
I should probably mention that I do not really have a great handle on how
package configurations work these days.
Coming back to Smalltalk after a long time away.
Pointer to an explanation of how package configurations work would be great.
--- End Message ---
Btw. there exists an updated version of Glorp:
github://pavel-krivanek/glorp:8.3.1-23-baseline
But the compatibility of it with SQLite was never tested
-- Pavel
so 19. 10. 2019 v 10:27 odesílatel Todd Blanchard via Pharo-users <
pharo-users@lists.pharo.org> napsal:
> I loaded GLORP+P3 without is
Hi Todd,
Both specify their dependency on Glorp almost the same way:
P3:
spec baseline: 'Glorp' with: [ spec repository:
'github://pharo-rdbms/glorp:master/'].
Sqlite3:
spec baseline: 'Glorp' with: [ spec repository: 'github://pharo-rdbms/glorp' ].
What exactly is the conflict ?
Sven
> On
--- Begin Message ---
I loaded GLORP+P3 without issue.
Trying to load SQLite3 - it also wants to load GLORP which complains of
conflict.
For P3 I used:
Metacello new
baseline: 'P3';
repository: 'github://svenvc/P3';
load: 'glorp'.
For SQLite:
Metacello new
repository: 'gith
> On 11 Oct 2018, at 02:26, Pierce Ng wrote:
>
> On Wed, Oct 10, 2018 at 11:12:37AM +0200, Sven Van Caekenberghe wrote:
>> I know that the actual PSQL DB that I am using has all the Glorp test
>> tables in it, I forgot whether that happened automatically or not.
>
> The Glorp test database is
On Wed, Oct 10, 2018 at 11:12:37AM +0200, Sven Van Caekenberghe wrote:
> I know that the actual PSQL DB that I am using has all the Glorp test
> tables in it, I forgot whether that happened automatically or not.
The Glorp test database is set up by "#GlorpDemoTablePopulatorResource
asClass invali
@lists.pharo.org] On Behalf Of
> Sven Van Caekenberghe
> Sent: Wednesday, 10 October 2018 11:13
> To: Any question about pharo is welcome
> Subject: Re: [Pharo-users] Glorp with P3
>
> Craig,
>
> I tried in a clean
> Pharo-7.0.0+alpha.build.1276.sha.6c09bd43b
: Re: [Pharo-users] Glorp with P3
Craig,
I tried in a clean
Pharo-7.0.0+alpha.build.1276.sha.6c09bd43bb0d76c18958c720649aaf6834870bb5 (64
Bit).
Load expression (as per https://github.com/svenvc/P3), which also loads Glorp
itself:
Metacello new
baseline: 'P3';
repositor
the support.
>
> I'm using Pharo 6.1 - 32bit stable.
>
> Craig
>
> -Original Message-----
> From: Pharo-users [mailto:pharo-users-boun...@lists.pharo.org] On Behalf Of
> Sven Van Caekenberghe
> Sent: Wednesday, 10 October 2018 08:56
> To: Any question about
t: Re: [Pharo-users] Glorp with P3
Hi Craig,
Last time I checked, this worked fine. I'll try again later today, what version
of Pharo are you using ?
Sven
> On 9 Oct 2018, at 15:43, Craig wrote:
>
> Hi All,
>
> I installed Glorp with P3 using the snippet on the P3 Github p
Hi Craig,
Last time I checked, this worked fine. I'll try again later today, what version
of Pharo are you using ?
Sven
> On 9 Oct 2018, at 15:43, Craig wrote:
>
> Hi All,
>
> I installed Glorp with P3 using the snippet on the P3 Github page.
>
> P3 seems to be working fine. The tests ar
Hi All,
I installed Glorp with P3 using the snippet on the P3 Github page.
P3 seems to be working fine. The tests are Ok. While working through the
Glorp book, I got as far as "session createTables" and then got a debugger
window.
It seems that the SQL is being sent to a variable in t
On 1 December 2017 at 13:46, Alistair Grant wrote:
> Hi Everyone,
>
> There haven't been any complaints about the merged version, and Glorp
> fails to load #development on Pharo 7, so I'm planning to update
> ConfigurationOfGlorp to:
>
> - Work on Pharo7 when given the #development symbolic versio
Hi Everyone,
There haven't been any complaints about the merged version, and Glorp
fails to load #development on Pharo 7, so I'm planning to update
ConfigurationOfGlorp to:
- Work on Pharo7 when given the #development symbolic version
- Make Glorp-AlistairGrant.130 the stable version - up from
Gl
Hi Everyone,
I've merged the changes in:
- Glorp-HerbyVojcik.127 and
- Glorp-AlistairGrant.129
into Glorp-AlistairGrant.130
127 and 129 were both based on 126, but had diverged. This brings
them back together.
The new version can be loaded using #development, e.g.:
Gofer it
smalltalkhubUse
Niall Ross wrote:
Dear Herby,
adding #includesKey: is certainly doable. If you look at callers above
and subcallers below #anySatisfyDefault: you will see the issues
involved. Your includesKey: needs the same degree of platform-awareness
that Glorp's #anySatisfy: and #allSatisfy: implementations
jtuc...@objektfabrik.de wrote:
Herby,
I must admit I've never used Dictionary Mappings with Glorp, so I don't
have an answer.
But I am a bit confused by your code examples. See below
Am 24.10.17 um 20:27 schrieb Herby Vojčík:
Hello!
I am using a DictionaryMapping in my code, and I wanted to
Tom Robinson wrote:
Hi Herby,
In my opinion, the way you found to make it work is the way it should
be. The reason is that the first way doesn't translate into SQL and the
second one does. It might be possible to add includesKey: functionality
but resolving that to SQL would be more complex. I w
Herby,
I must admit I've never used Dictionary Mappings with Glorp, so I don't
have an answer.
But I am a bit confused by your code examples. See below
Am 24.10.17 um 20:27 schrieb Herby Vojčík:
Hello!
I am using a DictionaryMapping in my code, and I wanted to use
#includesKey: in #where:
Hello!
I am using a DictionaryMapping in my code, and I wanted to use
#includesKey: in #where: clause (something akin
each tools includesKey: aToolId
) to select only rows for which DictionaryMapping uses certain key. It
failed with the error in the lines of "#tools does not resolve to
fi
Hello!
I have the problem with mapping dictionary of key to simple data-holding
object (two integers) work. Glorp DictionaryMapping dicriminates between
mapping a simple value (#dictionaryFrom: String to: Integer), where
things work as assumed (having two fields in a table, one for key, one
f
On August 24, 2017 7:26:00 AM GMT+02:00, "jtuc...@objektfabrik.de"
wrote:
>Am 23.08.17 um 11:08 schrieb Herby Vojčík:
>> jtuchel wrote:
>>> Herby,
>>>
>>> as Esteban already said, UPSERT doesn't make any sense in an ORM. It
>>
>> I don't know... I just create new object (with same "primary key"
Am 23.08.17 um 11:08 schrieb Herby Vojčík:
jtuchel wrote:
Herby,
as Esteban already said, UPSERT doesn't make any sense in an ORM. It
I don't know... I just create new object (with same "primary key") and
register it (yes, I know I get an error - maybe I should be able to
set the policy to
jtuchel wrote:
Herby,
as Esteban already said, UPSERT doesn't make any sense in an ORM. It
I don't know... I just create new object (with same "primary key") and
register it (yes, I know I get an error - maybe I should be able to set
the policy to "overwrite" and it would makes sense; or not
Herby,
as Esteban already said, UPSERT doesn't make any sense in an ORM. It either
knows the object as one that has been read in this session or not. If not,
it is new and needs to be inserted.
You could, of course, try and see what happens if you let Glorp's insert
operation always issue an U
Hello!
Is there some way to do insert-or-update operation (that is, roughly, to
be able to register an object with possibly existing primary key(s) and
let it be written regardless?
Thanks, Herby
P.S.: Use case - I want to have log of USER-DEVICE pairing with last
timestamp and 'enabled' fi
Esteban A. Maringolo wrote:
2017-08-06 8:05 GMT-03:00 Herby Vojčík:
Guillermo Polito wrote:
How did you install garage and glorp? Catalog, configurations? Can you
paste here the installation instructions you followed?
Just adding GarageGlorp as dependency:
configuration: 'Gar
2017-08-06 8:05 GMT-03:00 Herby Vojčík :
> Guillermo Polito wrote:
>>
>> How did you install garage and glorp? Catalog, configurations? Can you
>> paste here the installation instructions you followed?
>
>
> Just adding GarageGlorp as dependency:
> configuration: 'GarageGlorp' with:
Guillermo Polito wrote:
How did you install garage and glorp? Catalog, configurations? Can you
paste here the installation instructions you followed?
Just adding GarageGlorp as dependency:
baseline: spec
spec for: #common do: [ spec
package: 'Towergame' with: [ spe
Pierce Ng wrote:
On Sun, Aug 06, 2017 at 12:54:41AM +0200, Herby Vojčík wrote:
Pharo is 6.1, Glorp, Garage etc. are #stable loaded from Pharo60
catalog (see attachment).
You may want to try GlorpSQLite. Load from Catalog Browser into a fresh 60510
image. All 889 tests should pass, as has been
On Sun, Aug 06, 2017 at 12:54:41AM +0200, Herby Vojčík wrote:
> Pharo is 6.1, Glorp, Garage etc. are #stable loaded from Pharo60
> catalog (see attachment).
You may want to try GlorpSQLite. Load from Catalog Browser into a fresh 60510
image. All 889 tests should pass, as has been the case since Ph
How did you install garage and glorp? Catalog, configurations? Can you
paste here the installation instructions you followed?
On Sun, Aug 6, 2017 at 1:37 AM, Herby Vojčík wrote:
> Herby Vojčík wrote:
>
>> Guillermo Polito wrote:
>>
>>> AFAIR, PharoDatabaseAccessor was meant to work with SqueakDB
Herby Vojčík wrote:
Guillermo Polito wrote:
AFAIR, PharoDatabaseAccessor was meant to work with SqueakDBX/DBXTalk
driver. No other driver should use it. At the time Garage did not even
exist.
So I'd say that you should not use PharoDatabaseAccessor with another
driver than the one it was origin
Guillermo Polito wrote:
AFAIR, PharoDatabaseAccessor was meant to work with SqueakDBX/DBXTalk
driver. No other driver should use it. At the time Garage did not even
exist.
So I'd say that you should not use PharoDatabaseAccessor with another
driver than the one it was originally mean to? I do no
Esteban A. Maringolo wrote:
Which version of Pharo, Glorp and SQLite are you using?
As for SQLite dll, I don't know (does it change the fact if
queryEncoding method is present?).
Pharo is 6.1, Glorp, Garage etc. are #stable loaded from Pharo60 catalog
(see attachment).
Herby
Esteban A
Which version of Pharo, Glorp and SQLite are you using?
Esteban A. Maringolo
2017-08-05 19:20 GMT-03:00 Herby Vojčík :
> Esteban A. Maringolo wrote:
>>
>> Herby,
>>
>> I regularly use `session login`, but I don't use SQLite in Pharo, but I
>> do in VisualWorks and it works just fine.
>> Maybe i
AFAIR, PharoDatabaseAccessor was meant to work with SqueakDBX/DBXTalk
driver. No other driver should use it. At the time Garage did not even
exist.
So I'd say that you should not use PharoDatabaseAccessor with another
driver than the one it was originally mean to? I do not know exactly your
setup,
Esteban A. Maringolo wrote:
Herby,
I regularly use `session login`, but I don't use SQLite in Pharo, but I
do in VisualWorks and it works just fine.
Maybe if there is a bug we should fix it. Even with a no-op method.
Regards!
Esteban A. Maringolo
It's hard. The problem is
PharoDatabaseAcces
Herby,
I regularly use `session login`, but I don't use SQLite in Pharo, but I do
in VisualWorks and it works just fine.
Maybe if there is a bug we should fix it. Even with a no-op method.
Regards!
Esteban A. Maringolo
2017-08-05 15:52 GMT-03:00 Herby Vojčík :
> Alistair Grant wrote:
>
>> Hi H
Alistair Grant wrote:
Hi Herby,
On 5 August 2017 at 18:09, Herby Vojčík wrote:
Hello!
First of all, what is preferred way to (first time) login into database? I
had the impression that `aDatabaseAccessor login` is sorta low-level, and
one should do `session login` (after all, it is session yo
Hi Herby,
On 5 August 2017 at 18:09, Herby Vojčík wrote:
> Hello!
>
> First of all, what is preferred way to (first time) login into database? I
> had the impression that `aDatabaseAccessor login` is sorta low-level, and
> one should do `session login` (after all, it is session you get to work
>
Hello!
First of all, what is preferred way to (first time) login into database?
I had the impression that `aDatabaseAccessor login` is sorta low-level,
and one should do `session login` (after all, it is session you get to
work with, not an accessor).
But with Garage SQLite, `session login`,
On Thu, Aug 03, 2017 at 03:27:16PM +0200, Herby Vojčík wrote:
> Looking at state of the art code:
> GlorpSession >> loginIfError: aBlock
> | result |
> result := self accessor loginIfError: aBlock.
> system platform characterEncoding: accessor encoding.
> ^result
In the lin
Pierce Ng wrote:
On Wed, Aug 02, 2017 at 11:30:27AM +0200, Herby Vojčík wrote:
Hm, I though that once I open a session it does actually connect on
demand (it has Login, system and all the information for it). Does
it actually mean that if I want to stay connected I must do `session
login` before
On Wed, Aug 02, 2017 at 11:30:27AM +0200, Herby Vojčík wrote:
> Hm, I though that once I open a session it does actually connect on
> demand (it has Login, system and all the information for it). Does
> it actually mean that if I want to stay connected I must do `session
> login` before each `sessi
jtuc...@objektfabrik.de wrote:
Herby,
I am not aware of any automatic reconnect tools. Kepping a DB connection
alive after an image is closed is surely not desired and chances are the
DB will close the inactive session eventually anyways.
Hm. When I though about it, image save / load cycle is
Herby,
I am not aware of any automatic reconnect tools. Kepping a DB connection
alive after an image is closed is surely not desired and chances are the
DB will close the inactive session eventually anyways.
So it's probably best to make the DB connections reconnect on demand.
That means tha
Hello!
ZnServers have its own register mechanism by which they listen when they
are tagged as such after image save and load.
I wonder if there is some way to connect to database in Glorp and then
"keep the connection" between image save/load. Or how is this managed
notmally in apps that use
Ah tx for the explanation.
I'm sure that I like bundles for the sake of them.
should not we removed DBXGlorp if it is not up to date?
Is BDXGlorp based on latest Glorp port?
GlorpDBX is nothing but a name to a Metacello config that used to load
both Glorp and the OpenDBX (now garageDB) dr
2016-10-02 2:37 GMT-03:00 stepharo :
> should not we removed DBXGlorp if it is not up to date?
>
> Is BDXGlorp based on latest Glorp port?
GlorpDBX is nothing but a name to a Metacello config that used to load
both Glorp and the OpenDBX (now garageDB) drivers.
Esteban A. Maringolo
should not we removed DBXGlorp if it is not up to date?
Is BDXGlorp based on latest Glorp port?
Le 1/10/16 à 08:36, Benoit St-Jean via Pharo-users a écrit :
0000 (UTC)
> Subject: Re: [Pharo-users] Glorp
> I typically use MySQL but since I'm into databases a lot, I'll probably play
> with PostgreSQL, DB2, Oracle, SQLite and SQL Server as well... I guess this
> port of Glorp also allows for an ODBC accessor or it only supports n
Renaud de Villemeur
To: Benoit St-Jean ; Any question about pharo is welcome
Sent: Friday, September 30, 2016 9:50 PM
Subject: Re: [Pharo-users] Glorp
Hi.
This documentation should give you the first
hint:https://ci.inria.fr/pharo-contribution/job/PharoBookWorkInProgress/lastSuccessfulB
Hi.
This documentation should give you the first hint:
https://ci.inria.fr/pharo-contribution/job/PharoBookWorkInProgress/lastSuccessfulBuild/artifact/book-result/Glorp/Glorp.html
It's still a work in progress, but the install part is accurate. Do you
plan to use it with Sqlite, or with MySql/po
--- Begin Message ---
Hello Pharoers,
I want to use Glorp and I am puzzled as to what to install.
I have found a few Glorp related package and I really don't know which one to
use nor which one is current. Besides, those packages are spread across
different websites.
So, which one should I use?
Hi Offray,
On Fri, Jun 10, 2016 at 09:37:58AM -0500, Offray Vladimir Luna C??rdenas wrote:
> On 09/06/16 23:39, Alistair Grant wrote:
>
> [...]
> >
> > I have seen one other problem with UDBC-SQLite3: if a connection is open
> > when the image is saved, it must be manually closed and re-opened a
Hi,
On 09/06/16 23:39, Alistair Grant wrote:
[...]
I've been able to define a couple of classes / tables with foreign keys
and it is all working fine. I'm still to set up a many-to-many
relationship and the more complex queries, but it is all looking good so
far.
I have seen one other probl
Hi Pierce,
On Thu, Jun 09, 2016 at 10:14:06PM +0800, Pierce Ng wrote:
> On Wed, Jun 08, 2016 at 08:25:27PM +0200, Alistair Grant wrote:
> > > asking the session to login results in the following:
> > > UDBCSQLite3Connection(Object)>>doesNotUnderstand: #queryEncoding
> > > PharoDatabaseAccessor>>en
On Wed, Jun 08, 2016 at 08:25:27PM +0200, Alistair Grant wrote:
> > asking the session to login results in the following:
> > UDBCSQLite3Connection(Object)>>doesNotUnderstand: #queryEncoding
> > PharoDatabaseAccessor>>encoding
> > GlorpSession>>loginIfError:
> > GlorpSession>>login
> > GlorpBookDes
Thanks Alistair
This is a great initiative. Documentation is our shared knowledge. I
spent time editing the document
but I do not have time and the need for glorp now.
Stef
Le 8/6/16 à 09:50, Alistair Grant a écrit :
Hi All,
I'm working my way through some of the examples in
PharoInProgre
On Wed, Jun 08, 2016 at 07:49:13PM +0200, Alistair Grant wrote:
> Hi Pierce,
>
> On Wed, Jun 08, 2016 at 09:22:10PM +0800, Pierce Ng wrote:
> > On Wed, Jun 08, 2016 at 09:50:41AM +0200, Alistair Grant wrote:
> > > PharoDatabaseAccessor DefaultDriver: GlorpSQLite3Driver.
> > > session := GlorpB
Hi Pierce,
On Wed, Jun 08, 2016 at 09:22:10PM +0800, Pierce Ng wrote:
> On Wed, Jun 08, 2016 at 09:50:41AM +0200, Alistair Grant wrote:
> > PharoDatabaseAccessor DefaultDriver: GlorpSQLite3Driver.
> > session := GlorpBookDescriptorSystem sessionForLogin: login.
>
> Listing 1.12 on page 9
On Wed, Jun 08, 2016 at 09:50:41AM +0200, Alistair Grant wrote:
> PharoDatabaseAccessor DefaultDriver: GlorpSQLite3Driver.
> session := GlorpBookDescriptorSystem sessionForLogin: login.
Listing 1.12 on page 9 of the PDF says your code is missing a line:
session login.
The example
Hi All,
I'm working my way through some of the examples in
PharoInProgress/Glorp. Adapting Pierce's code from his announcement:
| workingDir dbName login session |
workingDir := SmalltalkImage current imagePath asFileReference parent
fullName
On Fri, Apr 03, 2015 at 07:20:40AM +0200, Sven Van Caekenberghe wrote:
> Yes, we have to fix that, but you also set it manually, no real need to patch
> the code:
Ok, wasn't sure what the encoding strategy should be. I'll patch
GlorpDatabaseLoginResource then.
Pierce
> On 03 Apr 2015, at 06:58, Pierce Ng wrote:
>
> Now that we know the PostgresV2 driver can talk to our database, using the
> Monticello browser, open the PostgresV2 repository and load the package
> GlorpDriverPostgreSQL. Here I had to edit
> NativePostgresDriver>>connectionArgsFromCurrentLogi
I'm on a roll. :-) I've written another blog post on installing Glorp with
PostgresV2 on Pharo 4.
To avoid this message looking like spam mail promoting my blog and devoid of
content, here's the slightly edited blog post, in its original Markdown format
sans JSON metadata.
Outside of Smalltalk, c
.pharo.org
Enviados: Jueves, 2 de Abril 2015 14:17:41
Asunto: [Pharo-users] Glorp with NBSQLite3 on Pharo 4
Hi all,
I've integrated NBSQLite3 into Glorp on the current Pharo v40592 beta image.
Details in my blog post here:
http://www.samadhiweb.com/blog/
Pierce
Hi all,
I've integrated NBSQLite3 into Glorp on the current Pharo v40592 beta image.
Details in my blog post here:
http://www.samadhiweb.com/blog/
Pierce
Hi torsten
thanks for your energy and push!
People around me :) Olivier and Guille are planning their work on databases.
Guille started to hack an API.
Stef
Le 19/1/15 22:03, Torsten Bergmann a écrit :
Hi Craig,
I've Glorp working with Pharo 4 and NBSQlite3 now without any problem.
That's why
tion about pharo is welcome
Subject: Re: [Pharo-users] Glorp on Pharo 4
A comma is indeed a (binary) message. It concatenates two Collections, like
Strings.
Please provide more details on how you try to connect and what error you
get, exactly.
> On 22 Jan 2015, at 08:26, Craig wrote:
>
A comma is indeed a (binary) message. It concatenates two Collections, like
Strings.
Please provide more details on how you try to connect and what error you get,
exactly.
> On 22 Jan 2015, at 08:26, Craig wrote:
>
> From: Sven Van Caekenberghe
> Sent: 22 January 2015 08:37 AM
>
>> What exac
From: Sven Van Caekenberghe
Sent: 22 January 2015 08:37 AM
> What exactly do you mean ?
>
> Reading the link above that seems to be correct, at first glance, maybe I
don't see it.
Sven,
Forgive me, I'm new to Pharo, but I'm sure that in Pharo you don't use
commas to separate parameters in a
mes
> On 22 Jan 2015, at 06:52, Craig wrote:
>
> From: Sven Van Caekenberghe
> Sent: 20 January 2015 01:40 PM
>
>> Using Glorp on top of the PostgresV2 driver (which uses just a network
> connection and no native code nor plugin)
>> should work on all platforms. Of course, you still have to insta
From: Sven Van Caekenberghe
Sent: 20 January 2015 01:40 PM
> Using Glorp on top of the PostgresV2 driver (which uses just a network
connection and no native code nor plugin)
> should work on all platforms. Of course, you still have to install
Postgres itself, but it can run on another machine to
-Original Message-
From: Sven Van Caekenberghe
Sent: 20 January 2015 01:40 PM
Hi Sven,
> Using Glorp on top of the PostgresV2 driver (which uses just a network
connection
> and no native code nor plugin) should work on all platforms. Of course,
you still
> have to install Postgres its
This is cool!
I will add it to the Glorp resources I'm building.
Stef
Le 20/1/15 10:41, Torsten Bergmann a écrit :
Hi Craig,
see below a quick guide. Tell me when it works.
Someone should do a video from that...
Thanks
Torsten
--
Hi Craig,
> On 19 Jan 2015, at 13:02, Craig wrote:
>
> Hi All,
>
> I see that Sven is active on this list. I've tried to use his excellent
> tutorial on his "concerning-pharo" blog to understand Glorp and to get my
> own instance of the demo app running on Pharo 4 and Postgres.
>
> I have not
Thanks Torsten,
The guide worked right out of the box.
Many thanks for your help.
Craig
-Original Message-
From: Torsten Bergmann [mailto:asta...@gmx.de]
Sent: 20 January 2015 11:42 AM
To: cr...@hivemind.net; Any question about pharo is welcome
Subject: Glorp on Pharo 4
Hi Craig,
see
Hi Craig,
see below a quick guide. Tell me when it works.
Someone should do a video from that...
Thanks
Torsten
For Windows:
- go to http
On Behalf Of
Torsten Bergmann
Sent: 19 January 2015 11:04 PM
To: Any question about pharo is welcome
Subject: [Pharo-users] Glorp on Pharo 4
Hi Craig,
I've Glorp working with Pharo 4 and NBSQlite3 now without any problem.
That's why it is now also in the config browser.
As you
Hi Craig,
I've Glorp working with Pharo 4 and NBSQlite3 now without any problem.
That's why it is now also in the config browser.
As you see from the repo I restructured a bit the "Glorp" package
to dig deeper into it and hopefully find the time updating the port
once I have access to the VW code
Hi All,
I see that Sven is active on this list. I've tried to use his excellent
tutorial on his "concerning-pharo" blog to understand Glorp and to get my
own instance of the demo app running on Pharo 4 and Postgres.
I have not burnt a lot of time on this yet, but I would like to know if this
com
>quick question, how can I get Glorp for Pharo? And DBXTalk?
>If anyone can provide me with some links it will be much appreciated
Did you see this article from Sven:
https://medium.com/@svenvc/reddit-st-in-10-cool-pharo-classes-1b5327ca0740
Code is loadable in Pharo 3.0 also from config browser
More reasons to consider SQLite as solid option:
50% faster than 3.7.17
The latest SQLite 3.8.7 alpha version (available on the download page
http://www.sqlite.org/download.html) is 50% faster than the 3.7.17 release
from 16 months ago. That is to say, it does 50% more work using the same
number
2014-10-06 14:11 GMT-03:00 Sanjay-M :
> what I was saying was supposing we write a server that alone only accesses
> the SQLite database. Users behave like clients accessing the server over
> TCP/IP.
> and the text i pointed to in my earlier mail detailed how such a scenario
> could be implemented.
what I was saying was supposing we write a server that alone only accesses
the SQLite database. Users behave like clients accessing the server over
TCP/IP.
and the text i pointed to in my earlier mail detailed how such a scenario
could be implemented.
If someone could write a small sample with sa
Pierce,
Thank you for the answers.
Is the wrapper thread safe?
I understan the library is thread-safe per se (at least in
Android+Java it is), so using the wrapper in Pharo (single-threaded at
the OS level) wouldn't cause issues. But I don't know how NativeBoost
plays here.
Regards!
Esteban A
Sanjay-M wrote:
> I was wondering if this approach could be adopted in developing a
> Client/Server application with a separate server component accessing the
> SQLite database (on a separate machine).
> If a template / model can be developed i am sure this can be very useful in
> creating large
I am thinking of situations where we cannot have a web server even on the
intranet - more like traditional servers accessed over TCP/IP
-
---
Regards, Sanjay
--
View this message in context:
http://forum.world.st/Glorp-NBSQLite3-tp4779996p4782972.html
Sent from the Pharo Smalltalk Users mai
On Fri, Oct 03, 2014 at 09:19:15PM -0700, Sanjay-M wrote:
> I was wondering if this approach could be adopted in developing a
> Client/Server application with a separate server component accessing the
> SQLite database (on a separate machine).
Using HTTP/S as the client-server protocol, have the w
On Fri, Oct 03, 2014 at 10:44:43PM +0200, stepharo wrote:
> Cool what is NBSQLite3 (a nativeboost version)? Nice. Would be nice
> once you API stabilize that we get a chapter or on NBSQLite3 :)
Yes, NativeBoost interface to SQLite. Yes, I plan to write a chapter
on it. :-)
Pierce
There is a discussion on developing client/server in Dolphin Smalltalk's
online documentation
http://www.object-arts.com/downloads/docs/index.html -> Appendix B ->
Application Patterns -> New Application #consequences.
I was wondering if this approach could be adopted in developing a
Client/Server
On 24/9/14 18:17, Pierce Ng wrote:
Hello,
I am pleased to report that I have gotten Glorp working with NBSQLite3
enough to run Sven's Reddit.st.
Cool what is NBSQLite3 (a nativeboost version)? Nice. Would be nice once
you API stabilize that
we get a chapter or on NBSQLite3 :)
As mentioned
1 - 100 of 154 matches
Mail list logo
