Conflict between Unique field module and Computed field module

Computed field module

First off, badass module, by the way. Just sayin.

This might be an issue without a resolution, but I thought I'd toss it out there, since having the Unique field module work with Computed fields module would allow most any cck field to be checked for uniqueness, regardless of whether it's integrated.

It seems that fields are checked for uniqueness prior to a computed field being built/edited, so a node can be saved with a non-unique computed field. What's more, for the same reason, any attempt to edit that node will be denied (since the computed field would be altered after the uniqueness check, but it never makes it that far)

In my case, I'm trying to check whether a location CCK field for postal code is unique (since Location module isn't integrated with Unique field). My thought was that I could add a computed field that used php to extract and format data from the postal code location field, then I could check that computed field for uniqueness. What I found was that unique fields allowed me to create a node with a non-unique computed field, but then when I went to edit that node, I was forever denied from saving changes.

Any insight would be totally appreciated! Or if I'm barking up the wrong tree, then perhaps you could reassign this as a Computer field issue?

Thank you, oh mysterious benevolent stranger of the future!