Can you elaborate a bit on this one?
Can you elaborate a bit on this one? This doesn't sound like expected behavior.
12 Replies
sure! here's me previewing the 'layers' table:
(notice how it ends at roblox_asset_id), but there is actually two hidden columns somehow..
so I go to edit table schema, and one of the hidden column is present here
when doing a manual query search they are both present here
recolor_roblox_asset_id and tint_hex
Interesting, thank you. This is certainly not expected. Will get a fix out!
thanks! just realized layer_order is also missing (that makes 3 hidden column)
just incase it was something to do with explicitly querying the 'tint_hex' column, i tried to do a select * and it works this way aswell
@astra can you give me the create script for your 'layers' table
Or
And can DM me or paste it here. I will try to reproduce it. Thanks 🙂
@Visal .In CREATE TABLE "layers" ( id INTEGER PRIMARY KEY AUTOINCREMENT, asset_id INTEGER NOT NULL, name TEXT NOT NULL, r2_key TEXT NOT NULL, created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP, body_part, recolorable BOOLEAN DEFAULT 0, roblox_asset_id, layer_order INTEGER DEFAULT 1, recolor_roblox_asset_id, tint_hex, FOREIGN KEY (asset_id) REFERENCES assets(id) ON DELETE CASCADE )
create table for assets if needed (since above has reference to assets)
CREATE TABLE "assets" ( id INTEGER PRIMARY KEY AUTOINCREMENT, name TEXT NOT NULL, category TEXT, created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP, canvas_r2_key TEXT, last_updated TIMESTAMP, pinned_tag TEXT , roblox_published BOOLEAN DEFAULT FALSE, roblox_published_at TIMESTAMP, user_id, preview_image_key TEXT, approval_status TEXT CHECK(approval_status IN ('pending', 'approved', 'rejected')), rejection_reason TEXT, approved_at TIMESTAMP, rejected_at TIMESTAMP, approver_id INTEGER, preview_roblox_asset_id TEXT)
Thanks so much. I can reproduce the problem now.
We didn't correctly handle when the column has no data type.
I will work on the fix. Thanks so much for reporting this edge case. It means a lot to us.
I believe it is fixed in the latest release 🙂
Let me know if you still encounter this problem 🙂
thank you very much! It works amazing now. great job on the new viewer!