| From: | Sean Davis <sdavis2(at)mail(dot)nih(dot)gov> |
|---|---|
| To: | pgsql-novice(at)postgresql(dot)org |
| Cc: | operationsengineer1(at)yahoo(dot)com |
| Subject: | Re: Application Data Storage Question |
| Date: | 2006-11-27 11:45:21 |
| Message-ID: | 200611270645.21303.sdavis2@mail.nih.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
On Monday 27 November 2006 01:41, operationsengineer1(at)yahoo(dot)com wrote:
> I'm working on an application that will need to store
> all sent and received emails in logical groupings - in
> my case, each transaction will have an email history
> associated with it.
>
> i can conceive of two ways to store the email data.
>
> 1. stick all pertinent email info in a db linked to
> the transaction id.
> 2. create a transaction id directory in the file
> system and store a file for each email sent/received
> with all the pertinent info within that file.
>
> the user needs this functionality to provide an
> archive of the transaction.
>
> i'm not experienced enough to know the pros and cons
> of either process, or if there is a better process i
> haven't thought of.
It sounds like you have storage and retrieval needs based on an index. Why
not use the database?
Sean
| From | Date | Subject | |
|---|---|---|---|
| Next Message | operationsengineer1 | 2006-11-27 15:55:05 | Re: Application Data Storage Question |
| Previous Message | Tom Allison | 2006-11-27 11:24:40 | Re: Benchmarking PostgreSQL against others on Windows? |