Thanks Dave,
I came up with the same answer after much googling. I managed to write a
trigger to do this and it worked first time :D
Then I realised I was going to have to write more triggers to handle the
reverse side, i.e. deleting a coach_train record after a booking has been
made.
Thanks
Hello all,
All right, it seems that everyone thinks saving a pdf into postgresql is
not a good idea.
My situation is:
=
. pdf file: 500kb
. One year I need to save around 65 files = 32M
As a summary, disadvantages are:
==
. Memory issue when
On Thu, May 19, 2011 at 09:39:54AM -0400, Emi Lu wrote:
> All right, it seems that everyone thinks saving a pdf into postgresql
> is not a good idea.
No.
> As a summary, disadvantages are:
> ==
> . Memory issue when read/save/retrieve the file
> . Increase load
T
On 05/19/2011 09:53 PM, Karsten Hilbert wrote:
On Thu, May 19, 2011 at 09:39:54AM -0400, Emi Lu wrote:
All right, it seems that everyone thinks saving a pdf into postgresql
is not a good idea.
No.
Hardly everyone. You lose transaction safety when using file system
storage outside the DB, y
Craig, Karsten,
Hardly everyone. You lose transaction safety when using file system
storage outside the DB, you need another way to talk to the server than
just the Pg connection, and most importantly your backups become more
complicated because you have two things to back up.
It's not simple,
