Hi,

I'm reading up on some of the backend databases that FPC & Lazarus supports via SqlDB.

* Is SQLite a local database only? Something like MS Access (Jet database)? Can you use it for client/server applications (web and GUI apps) via TCP/IP networking?

* Anybody got some good or bad points regarding PostgreSQL? Last night I read about PostgreSQL for the first time. The feature list is very impressive and it seem to be right up there with MS SQL Server and friends. Anybody know how resilient it is to database corruptions (possibly due to power failures) etc... I know Firebird handles such cases pretty well.

Regards,
- Graeme -

I have had a couple of power failures with Postgres (living in SA an' all :) and it did handle those without any hiccups. I found Postgres to be very easy to access via FPC/Lazarus and it is the only db I use. I found the trigger functions(written with PL/pgSQL) can handle any logic I cared to invent and grammatically very similar to Pascal, making it easy to learn.

HTH

Alex du Plessis wrote

> I have had a couple of power failures with Postgres (living in SA an' all :) and it did handle those without any hiccups.

Exactly what I wanted to hear, seeing that our clients don't bother investing in UPS's and we are based in South Africa as well. :-)

I found Postgres to be very easy to access via FPC/Lazarus and it is

Brilliant, thanks for the response.

Regards,
- Graeme -

Yes, SQLite is a flat file database manager without any networking support, so it is local access only.

PostgreSQL is intended to be even better than SQL Server, as its reference point is Oracle. It handles power outages very well, as it uses journalling to keep track of in-flight transactions.

Just be aware that PostgreSQL is not a "lite" DBMS in any way. To get the best from it you need to configure the communications side of things when you first install the software, and you need to design your tables and tablespaces properly. Note that with its tablespaces spread over multiple physical disks, PostgreSQL can have multiple physical I/O operations running concurrently. This means that transaction times can be slashed by sensible physical data modelling.

There is a hierarchy of Usenet newsgroups for supporting PostgreSQL;
their names all begin with "pgsql".

En/na Graeme Geldenhuys ha escrit:

http://sqlite.org/whentouse.html

I've been using sqlite with fpc/lazarus (though using zeos or direct access instead of sqldb) as an embedded, simple, database for a handful of projects that run mostly unattended 24 hours a day and so far it's worked well.

I'm not using it with fpc (my deployed applications fits more the embedded sqlite model than the more complex client/server one) but I'm using it for our internal time tracking application and it gave us no problem in the last 4 years, it was a set-up and forget thing.

Bye

I'm using pgsql for at least 10 yrs, some of our clients have really big databases - never run into problem with it. It works like a charm and it's really robust.At this time we finished porting of our ERP software to qtlcl and first copies are installed at customer site, first feedback is positive :) Using zeoslib ....

zeljko

zeljko wrote

I'm using pgsql for at least 10 yrs, some of our clients have really big databases - never run into problem with it.

It seems PostgreSQL scales very well. Currently the largest database in the world is by Yahoo and run on PostgreSQL topping out at 2 Petabyte in size and that processes 24 billion events a day.

http://it.toolbox.com/blogs/oracle-guide/worlds-largest-database-runs-on-postgres-24979

From the PostgreSQL mailing list, it seems 300GB?1TB database are pretty normal as well. So our clients should be pretty happy with there 300?600 Megabyte databases. ;-)

Thanks to all that replied.

Regards,
- Graeme -