Repository navigation
chore: version packages - #47
Open
github-actions[bot] wants to merge 1 commit into
Open
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@maple-dev/effect-orm@0.7.2
Patch Changes
$.a.sub($.b.add(1))compiles toa - (b + 1), nota - b + 1. Chains still follow SQL precedence as documented ($.a.sub(1).div(2)isa - 1 / 2); passing the group as an argument is how to group.$.Ids.eq([0, 4294967296])writesCAST([0, 4294967296] AS Array(Nullable(Int64))). Uncast, ClickHouse inferred the literal's element type from its values (Array(UInt64)here) and could refuse the comparison withILLEGAL_TYPE_OF_ARGUMENT.5e-324) was a syntax error and is now written from its bits; a whole number past 2^53 (44812297868494010) was written as its shortest decimal, which ClickHouse parses as a different integer, soWHERE x = valuecould miss the row — it is now written as the double's exact integer value.select()over a subquery or union (CH.fromQuery(inner, "w").select(),CH.fromUnion(union, "u").select()) selects every alias the source selects, as its type already said. It died withQueryBuilderDefect: select() is required, because the derived source has no column list until its own SELECT is evaluated.param.of(type)selected on its own is writtenCAST($n AS <type>), so a boolean or array comes back as itself instead of text that fails to decode. A fractional value compared with an integer column binds as$n::numericinstead of failing withinvalid input syntax for type bigint. Nothing else is cast: whole numbers, params compared with columns, inserts andrealcolumns keep untyped placeholders (and their indexes).param.ofalso no longer confuses two types that share a codec (int8andfloat8).QueryBuilderError(InvalidLiteral) instead of throwing: a bigint compared against a non-integer column, a non-stringlike/notLike/ilikepattern,lit()of anything but a string or number (it wrote[object Object]), a non-numeric arithmetic operand, an invalidDate, and an unparseable string or invalidDatefor a Postgres timestamp. A non-expression in aselectrecord is aQueryBuilderDefectnaming the alias, like a malformedorderBy.Need help on this PR? Tag
@codesmith-botwith what you need.