O Alvaro Herrera έγραψε στις Jan 31, 2006 :
> Jacob Costello wrote:
>
> > Has anyone tried using a postgres based solution for archiving email for
> > regulatory purposes ?
>
> I don't know about regulatory purposes, but the Oryx software is
> designed for that: http://www.oryx.com (or .net, don
Jacob Costello wrote:
> Has anyone tried using a postgres based solution for archiving email for
> regulatory purposes ?
I don't know about regulatory purposes, but the Oryx software is
designed for that: http://www.oryx.com (or .net, don't remember)
--
Alvaro Herrera
Can anyone tell me how the searchable email archive on the postgres site
is implemented. Is postgres used as part of the back end ?
Has anyone tried using a postgres based solution for archiving email for
regulatory purposes ?
Jake Costello
---(end of broadcast)--
- Original Message -
From: "Mario Splivalo" <[EMAIL PROTECTED]>
Yes, I'm tied to the pgadmin3 for the moment, so there's nothing I could
do. It's a pain to develop a database such way.
Mario,
If you keep your definition in a script file, you can copy the script and
paste it into pg
On Tue, 2006-01-31 at 12:30 +, Richard Huxton wrote:
> Mario Splivalo wrote:
> > When I create a view, I like to define it like this (just representing
> > the form here):
> [snip]
> > But, when I extracit it from postgres, it's somehow stored like this:
> [snip]
> > The later is much more hard
Mario Splivalo wrote:
When I create a view, I like to define it like this (just representing
the form here):
[snip]
But, when I extracit it from postgres, it's somehow stored like this:
[snip]
The later is much more hard to read, and when I need to change the view,
i get rash and stuff :)
Is
When I create a view, I like to define it like this (just representing
the form here):
CREATE VIEW vw_my_view
AS
SELECT
t1.col1,
t2.col2
FROM
t1
JOIN t2
ON t1.col1 = t2.col3
WHERE
t2.col4 = 'bla'
But, when I extracit it from postgres, it's