Smalltalk › Cincom › VisualWorks

To include in base, was: [7.4.1]Time zone question

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

23 messages Options

Mark Pirogovsky-3

Re: To include in base, was: [7.4.1]Time zone question

I second Jan's opinion about PostgreSql -- very efficient and scalable
DB. We use it for the mission critical applications beside store, on
modest Linux box, and it performs quite well under load. I also have it
installed on my 4 year old laptop, which I can put on network, if needed
it to be a shared db server, or use it as a personal DB, when I am on
the road.

We just need to realize that SQLLite is very good in addressing limited
set of problems i.e. embedded application, which do not require separate
installation, or separate server processes. And since it is file based
it may be susceptible to failures associated with the file based DB...

If my opinion counts, I'd say, it would be a great Idea for Cincom to
includes the SQLlite DB populated with the Store for the current
version, with the Standard distribution. It will be a huge time saving
for us, as we tend to publish the major VW versions into our store DB.

Just my 2c.

Weerts, Jan wrote:

> Hi all!
>
> Jim Guo wrote:
>> Dave Stevenson wrote:
>>> Is SQLite3 a better choice than PostgreSQL?
>
> N.B.: I have no direct experience with SQLite and I "maintain"
> our postgresql installation for the shared store code repository.
>
> In my opinion an answer to this question depends heavily on
> the planned use of the code repository.
>
> As a personal store database, which is also usable offline,
> SQLite seems to be quite suitable, since it is small and simple
> to use.
>
> PostgreSQL took a huge step forward concerning possible acceptance
> in providing an installer for Windows since version 8.1. It still
> is a full fledged database without a "plug it into my app" support,
> so there are a lot of tweakable parameters. This might be too much
> for a single user installation.
>
> For a multi user installation I prefer PostgreSQL. As I see it, the
> main advantages compared to SQLite are:
> - separate database processes:
> if you break your smalltalk image (which I do so about once a
> week), there is a chance, that a database running in the same
> system process can be affected/damaged.
> - multi user:
> - there are no locking issues with the "database file"
> - PostgreSQL scales very well with more users, heavy load
> and more database content
>
> Just my $0.02
> Jan

Stefan Schmiedl

Re: To include in base, was: [7.4.1]Time zone question

On Tue, 22 Jan 2008 09:38:10 -0500
Mark Pirogovsky <[hidden email]> wrote:

> If my opinion counts, I'd say, it would be a great Idea for Cincom to
> includes the SQLlite DB populated with the Store for the current
> version, with the Standard distribution. It will be a huge time saving
> for us, as we tend to publish the major VW versions into our store DB.

A Store matching the base image? Brilliant! I want one, too!

s.

Stew MacLean

RE: To include in base, was: [7.4.1]Time zone question

In reply to this post by Mark Pirogovsky-3

My 2c...

When I started with VW I decided to postpone using Store as I wanted to
concentrate on Smalltalk, not managing a RDBMS and code repository. (and
Store seemed immature at that stage). I intended to do this later.

As it happens, I've built a single click multi platform executable build
system based around Parcels, intending to convert it to Store later.

In retrospect, this is probably short-sighted, as I've now got more
pressing things to do than "conversion".

So, if VW had come configured to use Store on SQLite out of the box I
would be in different position, as I would have just used it. If at some
point I require multi-user code management, then I imagine it would be
straight forward to migrate to a more industrial strength RDBMS.

In summary, I second VW being shipped configured to use SQLite out of
the box, as the gap is not as wide between using Parcels and Store for
code management.

Cheers,

Stewart

>-----Original Message-----
>From: Mark Pirogovsky [mailto:[hidden email]]
>Sent: 23 January 2008 3:38 a.m.
>To: [hidden email]
>Cc: Weerts, Jan; [hidden email]
>Subject: Re: To include in base, was: [7.4.1]Time zone question
>
>I second Jan's opinion about PostgreSql -- very efficient and scalable
>DB. We use it for the mission critical applications beside store, on
>modest Linux box, and it performs quite well under load. I also have

it
>installed on my 4 year old laptop, which I can put on network, if
needed
>it to be a shared db server, or use it as a personal DB, when I am on
>the road.
>
>We just need to realize that SQLLite is very good in addressing
limited
>set of problems i.e. embedded application, which do not require
separate

>installation, or separate server processes. And since it is file based
>it may be susceptible to failures associated with the file based DB...
>
>If my opinion counts, I'd say, it would be a great Idea for Cincom to
>includes the SQLlite DB populated with the Store for the current
>version, with the Standard distribution. It will be a huge time saving
>for us, as we tend to publish the major VW versions into our store DB.
>
>Just my 2c.
>
>Weerts, Jan wrote:
>> Hi all!
>>
>> Jim Guo wrote:
>>> Dave Stevenson wrote:
>>>> Is SQLite3 a better choice than PostgreSQL?
>>
>> N.B.: I have no direct experience with SQLite and I "maintain"
>> our postgresql installation for the shared store code repository.
>>
>> In my opinion an answer to this question depends heavily on
>> the planned use of the code repository.
>>
>> As a personal store database, which is also usable offline,
>> SQLite seems to be quite suitable, since it is small and simple
>> to use.
>>
>> PostgreSQL took a huge step forward concerning possible acceptance
>> in providing an installer for Windows since version 8.1. It still
>> is a full fledged database without a "plug it into my app" support,
>> so there are a lot of tweakable parameters. This might be too much
>> for a single user installation.
>>
>> For a multi user installation I prefer PostgreSQL. As I see it, the
>> main advantages compared to SQLite are:
>> - separate database processes:
>> if you break your smalltalk image (which I do so about once a
>> week), there is a chance, that a database running in the same
>> system process can be affected/damaged.
>> - multi user:
>> - there are no locking issues with the "database file"
>> - PostgreSQL scales very well with more users, heavy load
>> and more database content
>>
>> Just my $0.02
>> Jan