Skip to content

fix(mysql): preserve null auto increment metadata - #101

Open
HandSonic wants to merge 104 commits into
mainfrom
fix/mysql-null-auto-increment
Open

HandSonic wants to merge 104 commits into
mainfrom
fix/mysql-null-auto-increment

Conversation

@HandSonic

Copy link
Copy Markdown
Owner

Summary

  • preserve SQL NULL for MySQL AUTO_INCREMENT table metadata
  • use ResultSet.wasNull() immediately after reading the nullable long
  • retain non-null increment values unchanged

Verification

  • red test returned 0 for a null AUTO_INCREMENT value
  • focused null/non-null metadata tests: 2 passed
  • MySQL module tests: 666 passed
  • plugin reactor package: succeeded
  • independent adversarial review: passed

HandSonic and others added 30 commits August 20, 2026 03:29
Add `visible` field to TableIndex domain model, read the `Visible` column
from SHOW INDEXES in MySQL metadata, generate INVISIBLE keyword in index
DDL, and add buildAlterIndexVisibility for ALTER INDEX syntax.

Frontend: add a "Visible" column to the index editor with a
VISIBLE/INVISIBLE toggle, disabled for primary keys, gated to MySQL only.

Test fixtures: init.sql, grants.sql, cleanup.sql, README.md under
script/test-fixtures/mysql/MYSQL-OBJ-006/.

Closes OtterMind#2574
Replace hardcoded INVISIBLE, ALTER INDEX strings with constants
SQL_INVISIBLE and SQL_ALTER_INDEX from MysqlSqlConstants.
…ABLE

buildAlterIndexVisibility was dead code: a visibility-only change fell
through to DROP+ADD, rebuilding the whole index. ALTER TABLE now emits
ALTER INDEX ... VISIBLE/INVISIBLE when the modified index differs from
the stored one only in visibility (and is not the primary key), and
falls back to the rebuild path otherwise.
Add `visible` field to TableColumn domain model, detect "INVISIBLE"
from the EXTRA column in information_schema, and generate the INVISIBLE
keyword in column DDL via MysqlColumnTypeEnum.

Frontend: add a "Visible" column to the column editor with a
VISIBLE/INVISIBLE toggle, gated to MySQL only.

Test fixtures: init.sql, grants.sql, cleanup.sql, README.md under
script/test-fixtures/mysql/MYSQL-OBJ-003/.

Closes OtterMind#2571
Replace hardcoded INVISIBLE string with SQL_INVISIBLE constant
from MysqlMetaDataConstants in MysqlColumnTypeEnum.
MySQL column grammar requires VISIBLE/INVISIBLE before the COMMENT
clause; the previous order produced ERROR 1064 for invisible columns
that carry a comment.
Adds a read-only Active Transactions view for the datasource node:
- Lists innodb_trx joined with processlist: transaction ID, state,
  start time, age, isolation level, rows locked/modified, thread ID,
  user, host, database, and current SQL.
- Works on MySQL 5.7 and 8.0; SQL text is null without PROCESS and
  surfaced as an explicit unavailable state instead of a blank value.
- New tree menu entry with a refreshable table dialog, i18n in all five
  locales, and MYSQL-OPS-002 fixtures (admin vs limited accounts).
…tolerant fallback

1. Add `resolveShellCandidates` method to return available shell candidates based on the operating system
2. Modify `create` method to sequentially try starting shells from the candidate list, automatically falling back to the next on failure
3. Add unit tests to verify shell candidate resolution and exception scenarios
4. Add compatibility handling for scenarios where enterprise security software blocks the default shell
…igurable default shell and improved shell candidate resolution

- Introduce DEFAULT_SHELL_PROPERTY configuration property for setting the default shell
- Add processFactory factory method to support custom process creation logic
- Refactor create method to accept pre-resolved shell candidate list
- Extract PtyProcess startup logic into a separate startProcess method
- Add proper argument configuration for PowerShell and CMD commands (-NoLogo, -NoExit, -Command, etc.)
- Improve shell candidate resolution order on Windows (pwsh → PowerShell → cmd)
- Add support for zsh and bash colored prompts
- Add test helper methods to reset factory and event publisher state
- Add comprehensive unit tests covering shell configuration and failover scenarios
- Change inner classes and enums to public to support external access
- Add command parser interface to support custom command lookup logic
- route DM SQL through the DM command executor
- add dedicated DM lexer and parser support
- retrieve execution plans through DmdbConnection.getExplainInfo
- preserve SQL type, metrics, streaming, and error behavior
- cover explicit EXPLAIN, Explain actions, cancellation, and driver isolation

Fixes OtterMind#2762
fix(dm): support EXPLAIN execution plans
openai0229 and others added 29 commits September 2, 2026 13:46
…pace-storage-quota

fix(workspace): keep local files out of localStorage
…erformance

perf(mysql): avoid full parse for ordinary completion scripts
refactor(terminal): refactor terminal shell startup logic with fault-tolerant fallback
…-column-2571

feat(mysql): invisible column management for MySQL 8.0.23+
…edit-actions

fix(result): stabilize sorting and edit actions
…active-transaction-2595

# Conflicts:
#	chat2db-community-client/package.json
…-theme-accent

fix(workspace): smooth panel resizing and restore theme accents
…ansaction-2595

feat(mysql): active InnoDB transaction inspection (OtterMind#2595)
…-expiration

fix(redis): persist no-expiration TTL updates
# Conflicts:
#	chat2db-community-client/package.json
#	chat2db-community-client/src/pages/main/workspace/components/WorkspaceExtend/GlobalExtendComponents/accountGrantsRequest.test.ts
#	chat2db-community-client/src/pages/main/workspace/components/WorkspaceExtend/GlobalExtendComponents/accountGrantsRequest.ts
…atest-request

fix(frontend): ignore stale account grants
@HandSonic
HandSonic force-pushed the fix/mysql-null-auto-increment branch from ac63c18 to 915dc92 Compare September 3, 2026 18:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants