| From: | Richard Broersma <richard(dot)broersma(at)gmail(dot)com> |
|---|---|
| To: | Arnaud Lesauvage <arnaud(dot)listes(at)codata(dot)eu> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Porting from MS Access 2007 to PostgreSQL |
| Date: | 2010-11-09 14:43:52 |
| Message-ID: | AANLkTinbvY-5a2USypK5+5O4LR5V2CmrpoFH-8A9YLha@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Nov 8, 2010 at 11:39 PM, Arnaud Lesauvage
<arnaud(dot)listes(at)codata(dot)eu> wrote:
> I can't really give you any advice about this, but we kept using Access as
> our Frontend and everything runs fine.
> You'll just have to make sure that you have read about the 'boolean <->
> integer' problem. This article is a nice start I think :
> http://www.postgresonline.com/journal/archives/24-Using-MS-Access-with-PostgreSQL.html
I've played with mapping access [yes/no] datatype to postgresql
BOOLEANs for a while. And after all of that *fun*, I've since started
mapping postgresql's INTEGER to access's [yes/no] datatype.
Life is so much better now because.
--
Regards,
Richard Broersma Jr.
Visit the Los Angeles PostgreSQL Users Group (LAPUG)
http://pugs.postgresql.org/lapug
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vick Khera | 2010-11-09 14:53:14 | Re: Full Vacuum/Reindex vs autovacuum |
| Previous Message | Allan Kamau | 2010-11-09 14:04:27 | Re: Why facebook used mysql ? |