Search Postgresql Archives

Re: [ADMIN] How to Prevent Certain Kinds of Joins?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





Scott Marlowe wrote:

Why not change the keys that currently connect them to something
different (i.e. random noise) and make a NEW table that could join them
with those random keys that is restriced access wise to only the chosen
few.

This might work rather nicely. It would enable us to restrict direct access to only a single table---a table with no purpose other than to faciliate a join of these two other tables. And staff that needs direct access to the original tables can continue to have it.


Or do you need to actually ever re-reference the two datasets?  If not,
then just lose the connecting data when you insert the rows.

Yes, unfortunately we do need to re-reference them. But I think the idea above will work out pretty well. Thank you for your help!


Heather

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux