[BUG] - Query result from scratchpad displays wrong columns

[UrbanMarco]

Describe the bug
I have the following query in the scratchpad

select s.id, s.state, p.id
from subscription.subscriptions s, product.plans p
where s.plan_id = p.id
and is_plan_available(p.activated_at, p.retired_at) = true
order by p.id;

when I run it, I am expecting to see a table with 3 columns: on the left the subscription IDs, in the middle the state of the subscription and on the right the plan ID.

However, WhoDB displays both on the left and on the right the plan ID.

To Reproduce
As explained above

Expected behavior
Same query but directly with PSQL

  id  | state |  id
------+-------+-------
 3102 |    16 |  5896
 2982 |    12 |  5896
 2910 |    16 |  5896
 2916 |    16 |  5896
 2920 |    16 |  5896

Screenshots

Additional context
Self-hosted version 0.45 with the following docker-compose file

version: "3.8"
services:
  whodb:
    image: clidey/whodb
    volumes:
      - ./sample.db:/db/sample.db
    # environment:
    #   WHODB_OLLAMA_HOST:YOUR_OLLAMA_HOST
    #   WHODB_OLLAMA_PORT:YOUR_OLLAMA_PORT
    ports:
      - "8081:8080"

[hkdeman]

Thank you for the great observation! This seems definitely an important issue. We will push out a fix for this soon. Will update this thread.

Meanwhile, I believe you could use SQL alias to get over this (incase it is a blocker).

[UrbanMarco]

Meanwhile, I believe you could use SQL alias to get over this (incase it is a blocker).

What do you mean? For the moment I went back to PSQL

[hkdeman]

Sorry I missed this message - I meant you could create an alias like this in SQL that will allow you to have unique column names and could work in Clidey.

Good news is that we have fixed this bug so you would not have to do that and leave the experience of PSQL behind.

Here is the PR: #332

Thank you for waiting and the great observation!

[UrbanMarco]

Thank you! I'll test this out