I see a lot of - I don't understand the database type, but I still want to use it - in this post.
Maybe the fact that Clickhouse is using SQL might make people think it is a relational database, but then they are wrong.
SQL is a DSL to write queries. So are there solutions to write SQL for MongoDB, SQL for Neo4j.
So SQl is not an one database type solution.
But it is still a good post to make people aware of Clickhouse.
What I try to explain here is that Clickhouse actually not is your ordinary relationship database. Clickhouse is a powerful beast but you need to know some things about it before you start. I hope it can help a few out there.
I started to use clickhouse 2 years ago and didn't have much knowledge about columnar databases then, so a lot of the stuff in the article are real world issues I assume many does.
My comment is not meant to shame you. It is a general observation about people adopting a different database type while not understanding it.
Another thing, besides thinking SQL is for relational databases, I see is that people use the relational mindset to structure other database types. If you don't structure the database the right way, the performance will be poor. And most of the times the database type will be blamed.
We all have a learning curve when we start using a unknown technology. The thing I learned over the years is to first get enough knowledge to find out what problem is the technology solving and how does it do that. And then start to explore if it helps you to solve the problem that made you look at the new technology.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I see a lot of - I don't understand the database type, but I still want to use it - in this post.
Maybe the fact that Clickhouse is using SQL might make people think it is a relational database, but then they are wrong.
SQL is a DSL to write queries. So are there solutions to write SQL for MongoDB, SQL for Neo4j.
So SQl is not an one database type solution.
But it is still a good post to make people aware of Clickhouse.
What I try to explain here is that Clickhouse actually not is your ordinary relationship database. Clickhouse is a powerful beast but you need to know some things about it before you start. I hope it can help a few out there.
I started to use clickhouse 2 years ago and didn't have much knowledge about columnar databases then, so a lot of the stuff in the article are real world issues I assume many does.
Anyway, thanks for reading and commenting.
My comment is not meant to shame you. It is a general observation about people adopting a different database type while not understanding it.
Another thing, besides thinking SQL is for relational databases, I see is that people use the relational mindset to structure other database types. If you don't structure the database the right way, the performance will be poor. And most of the times the database type will be blamed.
We all have a learning curve when we start using a unknown technology. The thing I learned over the years is to first get enough knowledge to find out what problem is the technology solving and how does it do that. And then start to explore if it helps you to solve the problem that made you look at the new technology.