Currently, the JDBCRC assumes that the tuple LFN,PFN is a unique entry and does not take the pool attribute into consideration. the underlying schema and associated queries need to be changed to have pool attribute as a first class element... any new column added should be called site though.

Relevant email from Scott Callaghan
I discovered I had an entry with no pool value:

[cybershk@shock CyberShake_PAS_pre_preDAX]$ pegasus-rc-client lookup PAS_fx_3806.sgt
PAS_fx_3806.sgt gsiftp://bw-gridftp.ncsa.illinois.edu:2811/scratch/sciteam/scottcal/SGT_Storage/PAS/PAS_fx_3623.sgt pool="None"

When I tried to insert a pool value for that entry, there was no change:

[cybershk@shock CyberShake_PAS_pre_preDAX]$ pegasus-rc-client insert PAS_fx_3806.sgt gsiftp://bw-gridftp.ncsa.illinois.edu:2811/scratch/sciteam/scottcal/SGT_Storage/PAS/PAS_fx_3623.sgt pool="bluewaters"
[cybershk@shock CyberShake_PAS_pre_preDAX]$ pegasus-rc-client lookup PAS_fx_3806.sgt
PAS_fx_3806.sgt gsiftp://bw-gridftp.ncsa.illinois.edu:2811/scratch/sciteam/scottcal/SGT_Storage/PAS/PAS_fx_3623.sgt pool="None"

This is surprising to me. I would like to be able to either 1) overwrite the previous pool value this way or 2) specifically have a way to set an already-existing attribute. It's a pain to delete and reinsert. Thanks!

-Scott