…ckDB engine (alibaba#134)

Fixes alibaba#131

Description
===========
- Server crashes with assertion failure when executing:
  INSERT IGNORE INTO t (col1) VALUES (57399)
  where col1 is a DATETIME column on a DuckDB engine table.
- The assertion `mon > 0 && mon < 13 && year <= 9999` in sec_since_epoch()
  (sql/tztime.cc:356) fails because the MYSQL_TIME struct contains month=0.
- InnoDB handles this case gracefully by truncating to zero date with a warning,
  but DuckDB engine crashes.

Cause
=====
- MySQL's SQL layer converts the invalid integer 57399 to a zero date
  (0000-00-00 00:00:00) via number_to_datetime() -> reset(), setting month=0.
- In the DuckDB write path, DeltaAppender::append_mysql_field() for
  MYSQL_TYPE_DATETIME2 calls TIME_to_gmt_sec() without validating the
  MYSQL_TIME struct, which triggers the assertion in sec_since_epoch().

Fix
===
- Add a zero/invalid date check (tm.month == 0) in the MYSQL_TYPE_DATETIME2
  branch of DeltaAppender::append_mysql_field() before calling TIME_to_gmt_sec().
- When a zero date is detected, compute the timestamp directly using calc_daynr(),
  consistent with the existing MYSQL_TYPE_NEWDATE handling.
- Valid dates (month in [1, 12]) continue to use the original TIME_to_gmt_sec() path.

Fixes alibaba#130

…aba#139)

When JSON functions (json_overlaps, json_depth, json_unquote) are called
from DuckDB engine with invalid input, they previously triggered MySQL
error handling (my_error) which is not appropriate in the DuckDB context.

This fix adds a `m_caller_is_duckdb` flag to the relevant JSON function
classes so that when called from DuckDB, errors are thrown as C++
exceptions (duckdb::InvalidInputException) instead of MySQL errors,
allowing DuckDB to handle them properly.

Fixes alibaba#136

Co-authored-by: Claude Opus 4.6 <[email protected]>

VECTOR columns stored as '/*!99999 vector(N) */ varbinary(4N)' in DD
caused INFORMATION_SCHEMA.COLUMNS/PARAMETERS/ROUTINES to return
'/*!99999' as DATA_TYPE instead of 'varbinary'.

Fix by adding SUBSTRING_INDEX(..., '*/ ', -1) to strip the versioned
comment prefix. Add EXTRA_IS_VERSION minor upgrade mechanism to
rebuild I_S views on existing installations without bumping upstream
IS_DD_VERSION.

Co-Authored-By: Claude Opus 4.6 <[email protected]>

On every published release whose tag starts with AliSQL-8.0.*,
  push the same tag to p1p1bear/alisql-docker so its existing
  build workflow can build and push the multi-arch Docker image
  to Docker Hub (songhuaxiong/alisql).

  Requires repo secret DOCKER_REPO_PAT (fine-grained PAT with
  Contents: read/write on p1p1bear/alisql-docker).

…libaba#150)

Build glibc 2.17 compatible AliSQL tarballs (x86_64 + aarch64) inside
  oraclelinux:7 on tag push, inject version from tag name into the version
  file, then create a GitHub Release with both tarballs attached.

  Triggered by tags matching AliSQL-8.0.* or AliSQL-5.7.*.