Hi!
I find myself in a situation where I need to delete large amount of data
from a huge (comparably) table, with relatively complex criteria on what
stays and what gets deleted:
- The table in question has about 6 million rows.
- The rows contain a mix of integer, timestamp and blob columns, w
Josef Kokeš wrote:
> 1) Am I overlooking some possible fast approach?
You could create a view named the same as your table and use it to
"mask" the table for the rest of application(s). This would save you
from inserting records twice. Let's assume your table is named DATA,
these would be the s
> I find myself in a situation where I need to delete large amount of data
> from a huge (comparably) table, with relatively complex criteria on what
> stays and what gets deleted:
>
> - The table in question has about 6 million rows.
> - The rows contain a mix of integer, timestamp and blob column
