Release v0.1.9

chore: Release cubrid-logtopbind-rs version 0.1.9

Release v0.1.5

chore: Release cubrid-logtopbind-rs version 0.1.5

Release v0.1.4

chore: Release cubrid-logtopbind-rs version 0.1.4

Release v0.1.3

Release v0.1.3: Bug Fix for Entry Processing

Bug Fix

Fixed an issue where entries were incorrectly deleted when:

1. The entry contained a question mark AND
2. There were no bind statements present

Previously, these entries were being deleted unnecessarily, significantly impacting results. When tested with a 50m logtop.q sample, this bug was causing valid entries to be discarded, resulting in only 2 entries being flagged for deletion instead of the correct number.
Let me help you write this todo/issue more clearly.

##Todo: Remove VARCHAR Type Inference in Bind Results

• The current implementation includes SQL types (e.g., VARCHAR) when generating bind results. While this provides useful information for analysis, it causes problems when attempting to rerun the scripts.

For more details, see the full changelog.

Release v0.1.2

chore: Release cubrid-logtopbind-rs version 0.1.2

Release v0.1.0

Full Changelog: https://github.com/vimkim/cubrid-logtopbind-rs/commits/v0.1.0