In-Process Analytical Data Management with DuckDB - posit::conf(2023)

Поделиться
HTML-код
  • Опубликовано: 25 ноя 2024

Комментарии • 6

  • @caty863
    @caty863 11 месяцев назад +2

    I find it a bit dishonest that you intentianally chose to use *RPostgreSQL* in your demo instead of the faster *RPostgres.*
    In addition, what's wrong with plain old SQLite? You should have elaborated a little deeper on what exact problem DuckDB is solving here.

    • @HarmonicaTool
      @HarmonicaTool 10 месяцев назад +1

      There are many talks on DuckDB. As much as I could take away: They claim to be faster than SQLite for typical analytical purposes because they store data in columns, not in rows. It is optimized for different purposes. It reads SQLite data directly.

    • @ravishmahajan9314
      @ravishmahajan9314 10 месяцев назад +2

      ​@@HarmonicaTool Its basically called Analytical SQLite. So SQLite is a lightweight database of applications from an OLTP perspective.
      Whereas DuckDB is for OLAP perspective. Means if you have lots and lots of application data and you want to analyze it in seconds, you can do it in duckdb as it is in memory analytics database.

    • @chalimsupa6603
      @chalimsupa6603 5 месяцев назад +1

      duckdb is designed for analytical workflows compared to sqlite which is a transactional db.

    • @chuckbecker4983
      @chuckbecker4983 4 месяца назад +5

      Accusing someone of dishonesty should be the last resort, used only after every other reasonable explanation has been identified and investigated. Going to dishonesty first exposes as much about the accuser as the accused.

    • @chalimsupa6603
      @chalimsupa6603 4 месяца назад +1

      @@chuckbecker4983 you are right.... as you said, it reveals more about the accuser. I think he could not find a better word to express his point. "Dishonest" is a very strong word and is not suitable in this context