On Mon, Mar 15, 2010 at 12:48:28PM -0000, Numérigraphe wrote:
> Just a thought: maybe it could be worked around by first inserting the row, then testing if the row respects the access rules with a select/where, and throwing an exception if it doesn't?
if that leads to the transaction being rolled back, it is a good workaround,
yes. It will make sure the entry does not stay in the database.
On Mon, Mar 15, 2010 at 12:48:28PM -0000, Numérigraphe wrote:
> Just a thought: maybe it could be worked around by first inserting the row, then testing if the row respects the access rules with a select/where, and throwing an exception if it doesn't?
if that leads to the transaction being rolled back, it is a good workaround,
yes. It will make sure the entry does not stay in the database.