Thanks for your videos. I had discovered duckdb lately. First thing to do was some data import from mysql, which turned out more annoying than I expected. In the end I used pandas, converted every single table from the mysqldb into a parquet file and then used duckdb on it. If you know a smarter and faster way, I'd be glad to hear.
thanks for the video. i just came to know about duckdb today. would you say it can be used as the main database? and what advantages would that have. also can be play the role redis plays in the sense of instead of hitting the main db on every request, requests hit the duckdb instead?
Hi Mark, Can you explain why querying sqlite from duckdb? I feel your tutorial focused more on how less on why. Would help if you tell us the use-case, Thank you
Hey - yeh so you'd mostly be doing that to get the benefit of DuckDB's super fast query engine when running analytics queries. But it could be fun to take a SQLite database and see if there is a difference in query speeds. I'll look into it!
@@learndatawithmark The tests are extremely visible if you are running against millions of records and applying complex queries - I like the duckdb cli tool, the outputs are very clean compared to sqlite
But the question is why would anyone do that? Why would query from DuckDB if i can directly query from SQLite😊 Do we have a strong use case? Second question is i don't get it what is the need to have DuckDB at first place? Is is another database like Snowflake or Redshift? I am asking these questions so that i can convince my clients. 😊
The reason would be that you want to use DuckDB's query engine, which is probably gonna be faster if you're doing analytical queries on large amounts of data. Would be fun to compare the tools against each other though.
Thanks for your videos. I had discovered duckdb lately. First thing to do was some data import from mysql, which turned out more annoying than I expected. In the end I used pandas, converted every single table from the mysqldb into a parquet file and then used duckdb on it. If you know a smarter and faster way, I'd be glad to hear.
It would be easier if there was a MySQL extension but right now there isn't - only Postgres and SQLite
thanks for the video. i just came to know about duckdb today. would you say it can be used as the main database? and what advantages would that have.
also can be play the role redis plays in the sense of instead of hitting the main db on every request, requests hit the duckdb instead?
Love you videos thanks man
Thank you for watching!
Hi Mark, Can you explain why querying sqlite from duckdb? I feel your tutorial focused more on how less on why. Would help if you tell us the use-case, Thank you
Hey - yeh so you'd mostly be doing that to get the benefit of DuckDB's super fast query engine when running analytics queries. But it could be fun to take a SQLite database and see if there is a difference in query speeds. I'll look into it!
@@learndatawithmark The tests are extremely visible if you are running against millions of records and applying complex queries
- I like the duckdb cli tool, the outputs are very clean compared to sqlite
But the question is why would anyone do that? Why would query from DuckDB if i can directly query from SQLite😊
Do we have a strong use case?
Second question is i don't get it what is the need to have DuckDB at first place? Is is another database like Snowflake or Redshift?
I am asking these questions so that i can convince my clients. 😊
The reason would be that you want to use DuckDB's query engine, which is probably gonna be faster if you're doing analytical queries on large amounts of data. Would be fun to compare the tools against each other though.