<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: Filtering table data by user in PostgreSQL</title>
	<atom:link href="http://blog.easytech.com.ar/2009/02/19/filtering-table-data-by-user-in-postgresql/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.easytech.com.ar/2009/02/19/filtering-table-data-by-user-in-postgresql/</link>
	<description>Technological Solutions</description>
	<pubDate>Thu, 09 Sep 2010 12:06:33 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7-bleeding</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: marcelo hamra</title>
		<link>http://blog.easytech.com.ar/2009/02/19/filtering-table-data-by-user-in-postgresql/#comment-3546</link>
		<dc:creator>marcelo hamra</dc:creator>
		<pubDate>Mon, 13 Jul 2009 08:41:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.easytech.com.ar/?p=402#comment-3546</guid>
		<description>this approach you've described is good when you have completely separate organizations but in many cases you need to manage access rights for groups and people inside the same organizations. 

In those cases you need a more dynamic approach. One could be to mark the 'owner' of the record, solving dynamically the access right to that record when someone else wants access. This approach could involve dynamic sql generation and business rules declared to manage access provileges.</description>
		<content:encoded><![CDATA[<p>this approach you&#8217;ve described is good when you have completely separate organizations but in many cases you need to manage access rights for groups and people inside the same organizations. </p>
<p>In those cases you need a more dynamic approach. One could be to mark the &#8216;owner&#8217; of the record, solving dynamically the access right to that record when someone else wants access. This approach could involve dynamic sql generation and business rules declared to manage access provileges.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
