Unique fields based on Location

Hi enzipher,

Thanks for your comments.

I reviewed how the Location module stores values for its fields, and found that it would require code specific to the Location module to be able to identify matching location values (whether you are using the Location module's fields as a CCK field or by itself).

This feature is beyond my current scope for development of this module. If you would like to sponsor development of this feature, please contact me by e-mail.

Working on a project that involves node creation for schools, and it seems that ensuring uniqueness of postal code fields would also go far in ensuring duplicates of schools didn't exist... Might prove true for any other organization that's expected to have a relatively thin distribution...

I'll try to look into this and share what I find :)

Thought I had a work-around involving Computed fields module, but ran into troubles. Might give someone else a lightbulb moment though, so feel free to check out the deets:
#831692: Conflict between Unique field module and Computed field module

I am interested in this functionality being added to the 7.x branch.

I'm closing it because the issue was created a long time ago without any further steps.

if you still need it then raise a new one.
thanks