strange insert
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 17.3k
- Forks
- 1.6k
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 28
Description
To reproduce
CREATE TABLE 'test' (
id VARCHAR,
name VARCHAR,
type VARCHAR,
num int,
disabled BOOLEAN,
created_at TIMESTAMP,
updated_at TIMESTAMP
) timestamp (created_at) PARTITION BY HOUR WAL;
ALTER TABLE test add COLUMN age int;
INSERT INTO test ( id, name, type, num, created_at ) VALUES ( 'xxx', 'string', 'string', 10, now() );
select * from test;
- why is
num0? - why is
updated_at1970?
QuestDB version:
8.1.0
OS, in case of Docker specify Docker and the Host OS:
windows docker desktop
File System, in case of Docker specify Host File System:
ntfs
Full Name:
xdewx
Affiliation:
xdewx
Have you followed Linux, MacOs kernel configuration steps to increase Maximum open files and Maximum virtual memory areas limit?
- Yes, I have
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running the reported CREATE TABLE, ALTER TABLE, INSERT, and SELECT sequence against QuestDB 8.1.0 and compare the num and updated_at values with the report. Trace the insert and schema-alteration behavior responsible for those values; done means explaining the behavior and providing a verified correction or documented expected result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100