You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With updates of Jline3 several more features came for !history which are supported without doing anything:
!history -d - Print timestamps for each event (sqlline default for !history)
!history -f - Print full time date stamps in the US format
!history -E - Print full time date stamps in the European format
!history -i - Print full time date stamps in ISO8601 format
!history -n - Suppresses command numbers
!history -r - Reverses the order of the commands
!history [first] [last] - These optional arguments may be specified as a number or as a string. A negative number is used as an offset to the current history event number. A string specifies the most recent event beginning with the given string.
It makes sense to reflect this features in sqlline doc also.
May be it also makes sense to have configurable property for history flags to use as default for !history
The text was updated successfully, but these errors were encountered:
With updates of Jline3 several more features came for
!history
which are supported without doing anything:!history -d
- Print timestamps for each event (sqlline default for!history
)!history -f
- Print full time date stamps in the US format!history -E
- Print full time date stamps in the European format!history -i
- Print full time date stamps in ISO8601 format!history -n
- Suppresses command numbers!history -r
- Reverses the order of the commands!history [first] [last]
- These optional arguments may be specified as a number or as a string. A negative number is used as an offset to the current history event number. A string specifies the most recent event beginning with the given string.It makes sense to reflect this features in sqlline doc also.
May be it also makes sense to have configurable property for history flags to use as default for
!history
The text was updated successfully, but these errors were encountered: