Hello, Does anyone have good ressources to design schemas/structure data for QuestDB?

Hi @Badr Bouslikhin. https://questdb.io/docs/concept/storage-model/ explains various bits about storage but feel free to share schema and ask concrete questions .

Thanks! I’ll look into it. I generally have no experience in design relational databases. I’ve been used to InfluxDB. I was doing research on best practices and design recommendations.

we also use the influxdb line protocol (albeit on TCP), so it should feel similar. We use tables and its a relational model, but dont necessarily need a schema upfront

Do you see any issue (or futur issue) with having tables composed of 33 columns? My current use-case is data collection from IoT temperature sensors sent through LoRaWAN. I collect the data using a webhook and a home-made Rust bridge. The messages are mostly composed of metadata (network link quality, device location computed by the network, device battery voltage, etc.).

33 columns is totally fine. We have some questdb specific things that are good to know: Symbol for repetitive strings: https://questdb.io/docs/concept/symbol/ Designated timestamp: https://questdb.io/docs/concept/designated-timestamp/ Time partitions: https://questdb.io/docs/concept/partitions/

Thanks for the feedback! I’ll go through the docs.

@Eugene would you be able to take a look at this one? thanks

Yes, the symbols must come before the columns, they cannot be mixed

Ok, thanks! Maybe it’s worth adding to the crate doc. or the https://questdb.io/docs/concept/symbol/ page.

The

column_str

method has no advantages over the

symbol

. In this case, the string will be implicitly converted to a symbol.