Maximilian Paulisch comments

Results 111 comments of


                                            Maximilian Paulisch

Explain leads to `bad value` error

Argh, sorry, I ran the reprex again and didn't check that it didn't contain the issue anymore. This only seems to happen when connection to SQLite before. Interesting.

Explain leads to `bad value` error

Seems to be fixed now 👍

Compilation on Windows latest + R3.6 seems to fail

Which version of R would you recommend for Windows?

FR: `dbWriteTable()` should compare input and output column names.

There is no possibility to directly get back the column names when creating the table, is there? dbplyr queries them via `SELECT * FROM WHERE 0 = 1` but of...

function translations for DATEDIFF and DATEADD

dbplyr doesn't know the column types, so it is not possible to simply translate `+` and `-` correctly for dates. Therefore, a custom function like `date_add()` and `date_diff()` would be...

`filter()` on boolean/legal variables only works with 1 and 0

What's the class of your connection?

Export a mask akin to rlang::.data for custom SQL functions

@hadley What do you think?

Inability to remove `window_order()` leads to weird, unpredictable results.

You can simply remove the window order via `df_g |> window_order()`. > It seems to me that the group_by(year) should remove the effects any previous window_order(). I'm not sure that...

Inability to remove `window_order()` leads to weird, unpredictable results.

Now you've lost me... Can you create a reprex and clearly state what's your issue? Otherwise I can't really help you.

Inability to remove `window_order()` leads to weird, unpredictable results.

Your reprex is very complicated. Please try to boil it down next time. I think the essence is caught by: ``` r library(dplyr, warn.conflicts = FALSE) library(dbplyr, warn.conflicts = FALSE)...