| From: | "Iavor Raytchev" <iavor(dot)raytchev(at)verysmall(dot)org> |
|---|---|
| To: | "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org>, "pgsql-interfaces" <pgsql-interfaces(at)postgresql(dot)org> |
| Subject: | pgaccess - where to store the own data |
| Date: | 2002-08-30 15:44:12 |
| Message-ID: | HKEIIDPFPDBMOMDLIEEGGENOCNAA.iavor.raytchev@verysmall.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-interfaces |
Hello everybody,
There is an open question we need broad opinion on.
Currently pgaccess stores its own data in the database it works with.
Some people do not like that. To store it elsewhere invokes a number of
issues such as:
- where is this somewhere
- converting form all versions to the new
- etc.
What do people think about this. Is it so bad that the own data is
stored in the database pgaccess works with?
Iavor
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2002-08-30 15:45:07 | Re: Accessing original TupleDesc from SRF |
| Previous Message | Joe Conway | 2002-08-30 15:33:40 | Re: Accessing original TupleDesc from SRF |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2002-08-30 15:50:52 | Re: [HACKERS] pgaccess - where to store the own data |
| Previous Message | Iavor Raytchev | 2002-08-28 17:15:14 | pgaccess 'weekly' release 5 is out |