Recent

Author Topic: PostgresSQL PQconnection - stability  (Read 4495 times)

timcs

  • Full Member
  • ***
  • Posts: 213
PostgresSQL PQconnection - stability
« on: July 19, 2013, 05:52:12 pm »
Hi

  At work , currently we have a PostgresSQL database set up which us used for very important information. I would like to use the PQconnection set up to write to a datetimestamp field, number field and a string/text field.

 My reason for this post is, is the PostgresSQL component(s) stable enough in this environment as I do not want to cause any issues with the system at work considering what it is used for.

Thanks

TimCS

BigChimp

  • Hero Member
  • *****
  • Posts: 5740
  • Add to the wiki - it's free ;)
    • FPCUp, PaperTiger scanning and other open source projects
Re: PostgresSQL PQconnection - stability
« Reply #1 on: July 19, 2013, 05:58:27 pm »
The postgresql driver has seen a lot of use, so I suppose it is quite stable (as is the Firebird one).

If you're not convinced/need further evidence/want to check things, there are unit tests you can run:
http://wiki.lazarus.freepascal.org/Databases#Running_FPC_database_tests

Patches with additional test cases more than welcome.
Want quicker answers to your questions? Read http://wiki.lazarus.freepascal.org/Lazarus_Faq#What_is_the_correct_way_to_ask_questions_in_the_forum.3F

Open source including papertiger OCR/PDF scanning:
https://bitbucket.org/reiniero

Lazarus trunk+FPC trunk x86, Windows x64 unless otherwise specified

goodname

  • Sr. Member
  • ****
  • Posts: 297
Re: PostgresSQL PQconnection - stability
« Reply #2 on: July 19, 2013, 07:54:09 pm »
Have used the PostgreSQL driver for for a number of years and can say that it has been stable for me. Couple of things to watch for with the Lazarus data controls.

The Lazarus data controls do not handle timestamp with time zone fields well. A simple workaround is to cast timestamptz fields to timestamp fields in your queries. If the field is defined as text then Lazarus data controls sees it as a blob field(ftMemo) by default. The simplest workaround is to cast the text field to varchar(255) in the query.

Dibo

  • Hero Member
  • *****
  • Posts: 1057
Re: PostgresSQL PQconnection - stability
« Reply #3 on: July 19, 2013, 10:42:21 pm »
I also confirm that postgres from sqldb is stable, we are using it in our company

exdatis

  • Hero Member
  • *****
  • Posts: 668
    • exdatis
Re: PostgresSQL PQconnection - stability
« Reply #4 on: July 20, 2013, 09:26:19 am »
I also confirm that postgres from sqldb is stable, we are using it in our company
Agree, I also have a couple of applications that work seamlessly on a network of 200 computers(PostgreSQL 9.2),
also I haven't a problem with migration(v8 to 9 etc)

timcs

  • Full Member
  • ***
  • Posts: 213
Re: PostgresSQL PQconnection - stability
« Reply #5 on: July 22, 2013, 05:54:34 pm »
Thanks to all for your input

The fields are formatted as:
id serial
connection_id integer
date timestamp without time zone
user_id integer
finsih date timestamp without time zone
username text

Any issues with these?

Thanks

TimCS

 

TinyPortal © 2005-2018