Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Definitions for Values Insertion #177

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

Definitions for Values Insertion #177

wants to merge 2 commits into from

Conversation

afs
Copy link
Contributor

@afs afs commented Jan 8, 2025

A replacement for substitute.

The context is taken from SEP-0007.

Currently, all new material is in a single section.

Submitting this PR puts the content under the WG agreement for IP and Licensing.


Preview | Diff

@afs afs changed the title Defintions for Values Insertion Definitions for Values Insertion Jan 8, 2025
@afs afs force-pushed the values-insertion branch from 3f606dd to f837588 Compare January 8, 2025 10:58
Comment on lines +10376 to +10378
<p>The following sections contain draft of material for a revised
"`exists`" operation.
</p>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<p>The following sections contain draft of material for a revised
"`exists`" operation.
</p>
<p>This section contains draft material for a revised
"`exists`" operation.
</p>

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a DRAFT pull request.

These are process notes. They will be removed.

spec/index.html Outdated Show resolved Hide resolved
This applies to `BIND`, variables introduced by `AS` in a `SELECT` clause, variables in a `VALUES`
clause, and variables intrucded by `AS` in `GROUP BY`.
</blockquote>
<p>Extend the "in-scope" rules to include the variables in-scope from the current row:</p>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<p>Extend the "in-scope" rules to include the variables in-scope from the current row:</p>
<p>Extend the "in-scope" rules to include the variables that are in-scope for the current row:</p>

spec/index.html Outdated Show resolved Hide resolved
spec/index.html Outdated
</table>
<p class="note">
This restriction means that <a href="#defn_valuesinsertion">values inserted</a>
do not conflict with values assigned to varibales with the pattern.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
do not conflict with values assigned to varibales with the pattern.
do not conflict with values assigned to variables with the pattern.

spec/index.html Outdated Show resolved Hide resolved

<p class="note">
A variable inside a project expression that is not in the variables projected
is not affected by the values insertion operation because it is renamed apart.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
is not affected by the values insertion operation because it is renamed apart.
is not affected by the value insertion operation because it is renamed apart.

Comment on lines +10373 to +10375
<!-- ValuesInsertion -->
<section>
<h3>Values Insertion and `EXISTS`</h3>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Values Insertion reads very oddly to me. Can this be changed (throughout) to Value Insertion?

Suggested change
<!-- ValuesInsertion -->
<section>
<h3>Values Insertion and `EXISTS`</h3>
<!-- ValueInsertion -->
<section>
<h3>Value Insertion and `EXISTS`</h3>

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is inserting multiple values.

<div>
<b>Definition: <span id="defn_valuesinsertion" name="defn_valuesinsertion">Values Insertion</span></b>
<p>
Define the Values Insertion function `ValuesInsert(X, μ)`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If, as I suggested above, Values Insertion is being changed to Value Insertion, then ValuesInsert should likewise be changed to ValueInsert

Suggested change
Define the Values Insertion function `ValuesInsert(X, μ)`
Define the Value Insertion function `ValueInsert(X, μ)`

<pre>exists(X) = true
if eval( D(G), ValuesInsert(PrjMap(X), μ) )
is a non-empty solution sequence.
exists(X) = false otherwise</pre>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
exists(X) = false otherwise</pre>
Otherwise, exists(X) = false.</pre>

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The style here is that for function definition, with each case being aligned. It is not running text.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants