From: | Raymond <support(at)bigriverinfotech(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Hiding Objects from ODBC Query |
Date: | 2003-08-16 18:51:25 |
Message-ID: | 200308161151.26347.support@bigriverinfotech.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Success with a fairly complex M$ Access database port ( if anything from
Access could be considered complex) to Postgres 7.3.4 on RH80.
Utilizes views, constraints, RI, triggers, PL/pgSQL functions, indices,
sequences, rules, groups, etc. The whole 9 yards.
Postgres is indeed a marvelous ORDB platform and development environment.
(would like to a little better java and python function support and examples
so I get away from #$(at)^& pl/sql :-)
Access clients tunnel via Windoz ssh client to a localhost'd Postgres daemon;
client connectivity is via current ODBC connector.
Client will be subsequently migrated to EJB-JSP or PHP in the near future.
Everything is great EXCEPT:
I cannot conceal system and other database objects that the end user does not
directly access. Database was configured for end users to utilize virtual
objects (views, with insert, update and delete privileges utilizing the
rewrite engine). While the end user cannot directly interact with other
database objects, he or she can view most all system and database relation
attributes and properties utilizing any ODBC query tool!!!
Help in concealing system and database objects please!
Raymond
From | Date | Subject | |
---|---|---|---|
Next Message | Jochem van Dieten | 2003-08-16 19:12:09 | Re: Dreamweaver |
Previous Message | Williams, Travis L | 2003-08-16 18:30:39 | Re: New to list, quick question. |