questdb / questdb/questdb

Some Keyword is used by spring boot but that is not supported..

Open
#519 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Compatibility New feature SQL
Dominant language
Java
Stars
17.3k
Forks
1.6k
Avg merge
5d 10h
Merged PRs (30d)
28

Description

Is your feature request related to a problem? Please describe.
When i am using java spring boot JPA then if i will make an entity class then it will automatically create new table inside my sql database and if table is already exist and using hibernate ddl-auto function then it will delete existing table and create new table.
Inside that if i will use Long datatype for variable then JPA automatically take that a bigserial and that is not supported by QuestDb but that is supported in SQL and also i am find the same scenario for String datatype as well.While use JPA pre-define query like findAll() i am not able to get resultset in the response.

Describe the solution you'd like
While Drop table automatically, JPA will use If_exist function but that is not supported by QuestDb.
so I would like to request you to give support those datatype which is used in JPA for automatically create table and drop table.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source files, tests, or entry points are identified in the issue. Start by clarifying which JPA/Hibernate schema-generation behaviors and datatypes QuestDB should support, including the reported query-result problem. Done should include agreed compatibility requirements and tests covering the supported behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, spring-boot, sql
Domain
backend, databases
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.