I think using "(ra - dr / cos_dec, ra + dr / cos_dec, ..." is better. Otherwise the actual box size will shrink towards the celestial poles. Also, adding boundary detection near RA~0/360 might be helpful.
I've been using astroquery for a while, which helped a lot in my research. Thanks anyway!
Actually it would be good to get rid of this workaround and use what sdss does with their radius search:
SELECT TOP 10 p.objid,
p.run, p.rerun, p.camcol, p.field, p.obj,
p.type, p.ra, p.dec, p.u,p.g,p.r,p.i,p.z,
p.Err_u, p.Err_g, p.Err_r,p.Err_i,p.Err_z
FROM fGetNearbyObjEq(258.25,64.05,3) n, PhotoPrimary p
WHERE n.objID=p.objID
alternatively define a dr_ra and dr_dec separately and use that one.
Most helpful comment
Actually it would be good to get rid of this workaround and use what sdss does with their radius search:
alternatively define a dr_ra and dr_dec separately and use that one.