Re: INSERT and .refresh() problems

On Monday 27 June 2005 04:47, Jacob Smullyan wrote:

> Perhaps new() should raise an error when not null unique constraints
> that aren't Sequences aren't provided to it, before the insert is
> submitted to the backend?  You'd then have bombed out a bit earlier
> and the error message would have been more relevant.

Yes, that could be a nice solution - even if not essential.

Anyway, the problem was MINE because I didn't use Sequence for a column that 
IS a sequence, and I've received an exception for my bad use of .refresh() 
- so, even if the exception doesn't explain well the error, it could be 
fine the current way.

-- 
Faber
http://www.faberbox.com/

Automate, automate, automate. Laziness is a virtue. -- John R. Daily


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click