Skip site navigation (1) Skip section navigation (2)

Re: M$ Access as fronted for pg with pgsqlodbc

From: "Richard Broersma" <richard(dot)broersma(at)gmail(dot)com>
To: oca(at)mvc(dot)edu(dot)ph
Cc: pgsql-odbc <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: M$ Access as fronted for pg with pgsqlodbc
Date: 2008-09-02 04:06:59
Message-ID: 396486430809012106l3d30f52fo462b1f08a21de65c@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-odbc
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

In response to

Responses

pgsql-odbc by date

Next:From: ocaDate: 2008-09-02 22:17:56
Subject: Re: M$ Access as fronted for pg with pgsqlodbc
Previous:From: ocaDate: 2008-09-02 01:59:06
Subject: M$ Access as fronted for pg with pgsqlodbc

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group