From: | oca(at)mvc(dot)edu(dot)ph |
---|---|
To: | pgsql-odbc(at)postgresql(dot)org |
Subject: | Re: M$ Access as fronted for pg with pgsqlodbc |
Date: | 2008-09-02 22:17:56 |
Message-ID: | 20080903061756.25o85uls848ogg0k@mail.mvc.edu.ph |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
Thank you! ----- Message from richard(dot)broersma(at)gmail(dot)com ---------
Date: Mon, 1 Sep 2008 21:06:59 -0700
From: Richard Broersma <richard(dot)broersma(at)gmail(dot)com>
Reply-To: Richard Broersma <richard(dot)broersma(at)gmail(dot)com>
Subject: Re: [ODBC] M$ Access as fronted for pg with pgsqlodbc
To: oca(at)mvc(dot)edu(dot)ph
Cc: pgsql-odbc <pgsql-odbc(at)postgresql(dot)org>
> On Mon, Sep 1, 2008 at 6:59 PM, <oca(at)mvc(dot)edu(dot)ph> wrote:
>
>
>> We are very much concerned about the speed, any tips to avoid while
>> developing application in M$ Access as front end?
>
> 1) do not use nullable booleans on the pg tables. the MS Jet engine
> sees null booleans as false. This makes rows with null booleans not
> update-able.
> 2) When ever possible, perform all large joins on the server not in
> the MS-Query editor.
> 3) SELELT * FROM LargeTable; can be slow, so try to include Where
> Clauses when ever possible to limit result set;
>
> --
> Regards,
> Richard Broersma Jr.
>
> Visit the Los Angeles PostgreSQL Users Group (LAPUG)
> http://pugs.postgresql.org/lapug
>
> --
> Sent via pgsql-odbc mailing list (pgsql-odbc(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-odbc
>
----- End message from richard(dot)broersma(at)gmail(dot)com -----
From | Date | Subject | |
---|---|---|---|
Next Message | oca | 2008-09-03 03:33:55 | using M$ ACCESS pass-thru query keep on asking for odbc authentication |
Previous Message | Richard Broersma | 2008-09-02 04:06:59 | Re: M$ Access as fronted for pg with pgsqlodbc |