Hi@mfussenegger,

The code is coming from CrateDB Toolkit, but is generally usable beyond there.

• https://github.com/crate/cratedb-toolkit/blob/v0.0.27/cratedb_toolkit/io/core.py#L17-L77
• Table Loader and MongoDB: A few refinements cratedb-toolkit#270

The idea is to have a concise code representationover here, for theBulkProcessor component, by abstracting away the handling of magic numbers from user-side code.

Because CrateDB Toolkit is rather heavy, and I wanted to make it reusable, I wanted to add it elsewhere. Another option would be to use the now separate cratedb-sqlalchemy package.BulkProcessor depends on it anyway, butBulkResponse doesn't, and would provide a generic little convenience wrapper around CrateDB's special responses to bulk requests.

The idea is to have a concise code representationover here, for theBulkProcessor component, by abstracting away the handling of magic numbers from user-side code.

That kinda confirms my point in that there's not much more code without the BulkResponse wrapper:

cursor=self.connection.execute(statement=statement,parameters=operation.parameters)self.connection.commit()cratedb_bulk_result=getattr(cursor.context,"last_executemany_result",None)failed_records=0success_count=0forresultincratedb_bulk_result:ifresult["rowcount"]==-2:failed_records+=1else:success_count+=1self._metrics.count_success_total+=success_countself.progress_barandself.progress_bar.update(n=success_count)

This to me would even be more readable as it avoids the additional indirection.

Also, given that the DB API spec says:

Return values are not defined.

I think we could extend our return value - as long as we can keep it compatible with the existing one.