Ι have the following table named discounts:
id Serialize
discount INT
offers JSON
With the following records
id | discount | offers
--- | --- | ---
1 | 10 | [{"type":"discount","percent":100},{"type":"freebie","id:100}]
2 | 0 | [{"type":"discount","percent":100},{"type":"freebie","id:100}]
...
CREATE TABLE discounts (id INT, discount INT, offers JSON);
INSERT INTO discounts VALUES
(1, 10, '[{"type":"discount","percent":100},{"type":"freebie","id":100}]'::JSON),
(2, 0, '[{"type":"discount","percent":100},{"type":"freebie","id":100}]'::JSON),
(2, 100, NULL);
SELECT * FROM dis...
14
This seemed to pop up at the same time as this bug.
Suddenly, asker's profile information is being pushed to the next line if the tags take up too much room:
I can't remember how this was handled previously, but I've never seen the profile pushed to the next line like that. I think the tags used...
I have following schema in PostgreSQL 12 (objects and their relations are versioned by date ranges):
CREATE TABLE tmp_deps (
id bigint,
code text,
name text,
start_date date,
end_date date
);
CREATE TABLE tmp_dep_parents (
department_id bigint,
parent_id bigint,
s...
