Most efficient db function to move all shapes in a design?

Thank you both for your responses.
Andrew, I am opening a case to look into the issue I am having with dbGetOverlaps().
I agree, the main issue has to do with the difference in how dbGetOverlaps() and geSelectArea()|geGetSelectedSet() produce their lists.
The difference between -nograph and a graphic session is more about how geSelectArea() is not an option for a -nograph session, and I keep thinking doing this non-graphically simply has to be more efficient.

I am working with a single layer mask reticle view with no hierarchy.
It is a flat design consisting only of shapes, and there are no shapes overlapping the selection bounding box.
I'm selecting die regions of the mask and comparing them with XOR to confirm the mask data in each region is identical.
Using results from the graphic session extractions, I have already confirmed the process works.

Lawrence, given the single layer, shape only, and flat nature of the design data, I don't think there would be any benefit to looping through the shapes within a selection bounding box. I can't cull the potential selection set by layer or object type. They are all the same in that respect. Writing a setoff(shapes cv~>shapes bbox<test>) loop seems like it would not be any more efficient than a predefined function. Is this what you are thinking might work better?

Without getting into the actual code, yes it is identical to the example code - with the understanding that to run it, I have the parent cellview open, and I use looping constructs to define different bbox, new cellnames, and new cell centerpoints for each selection area and leMakeCell().

Thank you both for your responses.
Andrew, I am opening a case to look into the issue I am having with dbGetOverlaps().
I agree, the main issue has to do with the difference in how dbGetOverlaps() and geSelectArea()|geGetSelectedSet() produce their lists.
The difference between -nograph and a graphic session is more about how geSelectArea() is not an option for a -nograph session, and I keep thinking doing this non-graphically simply has to be more efficient.

I am working with a single layer mask reticle view with no hierarchy.
It is a flat design consisting only of shapes, and there are no shapes overlapping the selection bounding box.
I'm selecting die regions of the mask and comparing them with XOR to confirm the mask data in each region is identical.
Using results from the graphic session extractions, I have already confirmed the process works.

Lawrence, given the single layer, shape only, and flat nature of the design data, I don't think there would be any benefit to looping through the shapes within a selection bounding box. I can't cull the potential selection set by layer or object type. They are all the same in that respect. Writing a setoff(shapes cv~>shapes bbox<test>) loop seems like it would not be any more efficient than a predefined function. Is this what you are thinking might work better?

Without getting into the actual code, yes it is identical to the example code - with the understanding that to run it, I have the parent cellview open, and I use looping constructs to define different bbox, new cellnames, and new cell centerpoints for each selection area and leMakeCell().