Duplicate SQL records versus unique constraints

[Arran Cudbard-Bell]

On 3/6/09 17:38, Alan DeKok wrote:
> Arran Cudbard-Bell wrote:
>> Thanks, i'll poke Alan and see if he wants to include it.
>
> $ git format-patch
>
>    :)

Still haven't had feedback on the last one yet !

>
>> It'd be nice
>> to have a generic
>> hashing module for string expansions and not have to do some much unlang
>> hackyness,
>> useful for CUI too.
>
> 	update reply {
> 	  User-Name := "%{md5:foo}"
> 	}
>
>    It's already there.
>

Ooooooo useful. Would you be adverse to a patch adding a policy section that provided the requisite behavior for both Access-Accept and Accounting-Request packets ? Or would you like two policy sections.

i.e. One that has a switch statement for packet type, or two different policies.

The advantage of the one policy is that it's listed with the same name in the require sections of the default config. The disadvantage is the added switch statement.

This is more of a general question for future patches... Do you want policies to be self contained, or do you not mind if they sprawl a bit.

Thanks,
Arran

P.S ProCurve switches don't include the Class attribute in Accounting-Requests. Already opened a case.

-- 
Arran Cudbard-Bell (A.Cudbard-Bell at sussex.ac.uk),
Authentication, Authorisation and Accounting Officer,
Infrastructure Services (IT Services),
E1-1-08, Engineering 1, University Of Sussex, Brighton, BN1 9QT
DDI+FAX: +44 1273 873900 | INT: 3900
GPG: 86FF A285 1AA1 EE40 D228 7C2E 71A9 25BB 1E68 54A2