Tiny typo in README.md

- Add InitializeIfNeeded() to trigger DuckDB initialization at startup
  when duckdb_mode=ON or DuckDB data files exist
- Add DataFilesExist() to check for duckdb.db or WAL files
- Call InitializeIfNeeded() in mysqld_main() after CreateInstance()
  to ensure WAL replay happens at startup rather than on first request
- Fix merge conflicts in wiki documentation files

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

* 'master' of github.com:alibaba/AliSQL:
  Update README.md
  MOD build.sh: use bundled tirpc to compile

- Restructure README.md with centered logo, badges, and feature tables
- Add usage examples for DuckDB analytics and vector search
- Add visual roadmap and star history chart
- Create README_zh.md for Chinese-speaking users
- Remove emoji icons for cleaner appearance

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

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

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

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

Add command-line option --sql-safe-updates to allow setting the global
default value for sql_safe_updates from the configuration file (my.cnf)
or command line.

Changes:
- Add opt_sql_safe_updates variable and source_sql_safe_updates for
  tracking the command-line option source
- Add --sql-safe-updates option to my_long_options array
- Synchronize the command-line value to global_system_variables.option_bits
  during server startup

This follows the same pattern used for --autocommit option, as Sys_var_bit
does not support command-line options directly.

Usage:
  # In my.cnf
  [mysqld]
  sql-safe-updates = 1

  # Or via command line
  mysqld --sql-safe-updates=1

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

Add introduction and quick start guide for rdsai-cli project
(https://github.com/aliyun/rdsai-cli) - an AI-powered database CLI
that supports natural language queries for AliSQL and MySQL.

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

…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