Changes in version 0.5.1.9000                      

                 Changes in version 0.5.1 (2026-05-26)                  

  - Updated identify_row() to accommodate changes in upcoming 'dbplyr'
    release - Thanks the 'dbplyr' devs for the fix!

  - fixed an error caused by changes in 'data.table'

                 Changes in version 0.5.0 (2026-01-08)                  

Bug fix

  - Fixed a bug in the apart feature in restrict_date() caused by
    'dbplyr' 2.5.1 update where the input order of the SQL translation
    for difftime() was flipped.

Improvements

  - Added a new define function with age restriction -
    define_case_with_age()

                 Changes in version 0.4.1 (2025-04-05)                  

Improvements

  - Functions that take remote table as input now checks whether
    connection to database is working properly.

                 Changes in version 0.4.0 (2025-02-28)                  

Improvements

  - fetch_var() documentation now indicates that it does not accept
    input from a pipe.
  - collapse_episode() now works for remote table input.
  - pool_case() now provides the source for the first valid and the
    latest records for linkage back to the source data.

                 Changes in version 0.3.1 (2024-05-23)                  

Bug fixes

  - Fixed a critical bug introduced by the new code that cleans the
    window order remaining in database output. The problem is related to
    this issue Inability to remove window_order() leads to weird,
    unpredictable results.

  - bind_source() will bind correctly if every variable name argument is
    a single string (i.e., selecting variables with common names only).

  - Fixed a bug in pool_case() when every source had all the flags, the
    code that fills missing flag == 1 would trigger an error.

                 Changes in version 0.3.0 (2024-05-15)                  

Improvements

  - fetch_var() will accept database input, but it will not prevent
    one-to-many joins because the checking could be slow on remote
    database.

  - All functions that accept database input now will NOT sort the
    output to avoid generating the 'ORDER BY' clause which may trigger a
    warning if the output was chained with subsequent operations.

  - restrict_date() will not check missing date unless the new
    check_missing argument was set to TRUE. The checking time may be not
    negligible for large database; the user should opt in for it.

Bug fixes

  - Chaining pool_case() with dplyr::compute() to create table in
    database should no longer give errors or warnings related to window
    order.

                 Changes in version 0.2.0 (2024-05-05)                  

Improvements

  - The apart argument in restrict_date() is now functional for both
    data.frame and database input.

  - restrict_date() will give warning if there are missing entries in
    date_var. The description of dup.rm has been re-written to clarify
    it is applicable only when apart is absent.

  - pool_case() now outputs both the number of raw (raw_in_src) and
    valid (valid_in_src) entries in each source.

  - List element of execute_def() output is named by definition and
    source labels.

  - Most of the verbose message, except data summaries, will be sent as
    message instead of text output, so that they can be suppressed via
    message = FALSE in Rmarkdown.

Bug fixes

  - Fixed if_date() gave output shorter than the input when detail and
    dup.rm are both TRUE. if_date() now does not assume the dates are
    sorted and returns elements in the original unsorted order.
  - Fixed restrict_date() for remote table might miss cases with
    duplicated dates when n > 2.