roll
@augusto-herrmann Thanks a lot for writing it down! Just trying to gather all the information now
@fjuniorr I think we can include it in the next version i.e. `v2.1`. I'm wondering when `namespace` can be applicable as I guess it's not a part of SQLite?
@fjuniorr Ahh I have forgotten about DuckDB. The Data Package spec itself in a form of a published data package is kinda hard to apply for classical client/server databases as...
I think the polars plugin is amazing! Technically both in frictionless-py codebase, and as a separate codebase are quite the same, so I would say that the only difference is...
> Agreed -- inferring compression from the path seems just fine. Do we get some other value from having a "compression" property that I'm missing? I will play a devil's...
> It's standard for file names to include compression type in their extension (file1.csv.zip, file2.csv.gz) I think it's more like a convention rather than a standard > Side note --...
@fjuniorr We can totally add `dialect.table` if there is a demand for it cc @dafeder
I think I mentioned it a somewhere during the v2 work but I see it this way as it was designed after data base design: `primaryKey`: array `uniqueKeys`: array of...
No, array of arrays https://datapackage.org/standard/table-schema/#uniqueKeys - so it's possible to define multiple unique combinations
@sapetti9 @peterdesmet Please take a look - https://github.com/frictionlessdata/datapackage/issues/new/choose I merged to make it visible, we can adapt if needed Also, I'm going to write this up in the contribution guide...