• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

andygrove / sqlparser-rs / 361

Build:
Build:
LAST BUILD BRANCH: fuzz
DEFAULT BRANCH: master
Ran 18 Jun 2019 11:56PM UTC
Jobs 1
Files 0
Run time –
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

pending completion
361

Pull #120

travis-ci

web-flow
[mssql] Parse CROSS/OUTER APPLY

T-SQL (and Oracle) support non-standard syntax, which is similar in
functionality to LATERAL joins in ANSI and PostgreSQL
<https://blog.jooq.org/tag/lateral-derived-table/>: it allows to use
the columns from the tables defined to the left of `APPLY` in the
"derived tables" (subqueries) to the right of `APPLY`. Unlike ANSI
LATERAL (but like Postgres' implementation), APPLY is also used with
table-valued function calls.

Despite them being similar, we represent "APPLY" joins with
`JoinOperator`s of its own (`CrossApply` and `OuterApply`). Doing
otherwise seemed like it would cause unnecessary confusion, as those
interested in dialect-specific parsing would probably not expect APPLY
being parsed as LATERAL, and those wanting to forbid non-standard SQL
would not be helped by this either.

This also renames existing JoinOperator::Cross -> CrossJoin to avoid
confusion with CrossApply.
Pull Request #120: [mssql/oracle] Support CROSS/OUTER APPLY
Jobs
ID Job ID Ran Files Coverage
1 361.1 18 Jun 2019 11:56PM UTC 0
92.25
Travis Job 361.1
Source Files on build 361
Detailed source file information is not available for this build.
  • Back to Repo
  • Travis Build #361
  • Pull Request #120
  • PR Base - master (#358)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc