WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content

Issue with Column Visibility When Setting read_only=true #39

@hmilbi

Description

@hmilbi

testdb.zip

Issue Description

When using the DuckDB Power Query Connector, I encountered an issue with column visibility based on the read_only parameter.

Steps to Reproduce

  1. Create a sample DuckDB database with a single table containing three columns:
    • int_column (integer)
    • varchar_column (varchar)
    • nvarchar_column (nvarchar)
  2. Add the data source in Power Query with read_only set to null:
    • All columns (int_column, varchar_column, nvarchar_column) are available in Power Query.
  3. Add the data source in Power Query with read_only set to true:
    • Only the int_column is visible in Power Query.

Expected Behavior

All columns (int_column, varchar_column, nvarchar_column) should be available regardless of the read_only setting.

Observed Behavior

Only the int_column is visible when read_only=true.

Environment Details

  • Version: v0.1.5
  • OS: Windows

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions