Fix duplicate columns in initialize-table-information

[tamurashingo]

Summary

Fixed the issue where initialize-table-information function retrieves duplicate column information when fetching table metadata.

Problem

When querying information_schema.columns with only table_name condition, it searches for tables with the same name across all databases (development, te
st, etc.) on the same MySQL instance, resulting in duplicate column information.

Observed Symptoms

• 27 rows of column information returned for a table with 11 columns
• Each column appears twice (retrieved from both dev and test databases)
• Unrelated columns from performance_schema are also included

Changes

MySQL (src/model/impl/mysql.lisp)

Added table_schema = database() condition to SQL queries in fetch-columns-and-types-impl and fetch-columns-and-types-plist-impl methods.

Before:

select column_name, data_type from information_schema.columns
where table_name = ?
order by ordinal_position

After:

select column_name, data_type from information_schema.columns
where table_schema = database() and table_name = ?
order by ordinal_position

PostgreSQL (src/model/impl/postgresql.lisp)

Added table_schema = current_schema() condition to SQL queries in fetch-columns-and-types-impl and fetch-columns-and-types-plist-impl methods.

Before:

select COLUMN_NAME, DATA_TYPE from information_schema.columns
where table_name = ?
order by ordinal_position

After:

select COLUMN_NAME, DATA_TYPE from information_schema.columns
where table_schema = current_schema() and table_name = ?
order by ordinal_position

Impact Scope

• Model initialization process for all MySQL-based models
• Model initialization process for all PostgreSQL-based models

Testing

• Confirmed existing tests pass
• Verified column information is not duplicated in environments with multiple databases

Related Issue

fix #139