Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: FarmerCodeY/AliSQL
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: master
Choose a base ref
...
head repository: alibaba/AliSQL
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: master
Choose a head ref
Checking mergeability… Don’t worry, you can still create the pull request.
  • 4 commits
  • 19 files changed
  • 3 contributors

Commits on May 11, 2026

  1. Fix VECTOR column DATA_TYPE in INFORMATION_SCHEMA views

    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 <noreply@anthropic.com>
    JoeJRW and claude committed May 11, 2026
    Configuration menu
    Copy the full SHA
    12726be View commit details
    Browse the repository at this point in the history

Commits on May 12, 2026

  1. ci: trigger alisql-docker build on release publish (alibaba#148)

    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).
    p1p1bear authored May 12, 2026
    Configuration menu
    Copy the full SHA
    687f38e View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    d06deb5 View commit details
    Browse the repository at this point in the history
  3. ci: add build-and-release workflow for tag-triggered tarball builds (a…

    …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.*.
    p1p1bear authored May 12, 2026
    Configuration menu
    Copy the full SHA
    dce1871 View commit details
    Browse the repository at this point in the history
Loading