Review databases "compiled to" from CAP Java by agoerler · Pull Request #2329 · capire/docs

agoerler · 2026-01-20T20:13:33Z

No description provided.

guides/databases/cdl-to-ddl.md

guides/databases/cap-level-dbs.md

guides/databases/cql-to-sql.md

Co-authored-by: Patrice Bender <patrice.bender@sap.com>

github-actions

Spelling Mistakes

guides/databases/cdl-to-ddl.md:196:22 Unknown word "slugified"
guides/databases/cdl-to-ddl.md:197:23 Unknown word "slugification"
guides/databases/cdl-to-ddl.md:197:120 Unknown word "slugified"
guides/databases/cdl-to-ddl.md:204:24 Unknown word "slugified"
guides/databases/cdl-to-ddl.md:205:70 Unknown word "slugified"

Generally, for each spelling mistake there are 2 ways to fix it:

Fix the spelling mistake and commit it.
The word is incorrectly reported as misspelled → put the word on the project-words.txt list, located in the root project directory.

github-actions · 2026-01-27T09:36:45Z

guides/databases/cdl-to-ddl.md


-> [!tip] Guaranteed & Stable Slugification
-> The slugification effects are guaranteed and stable, which means that you can rely on it and use the slugified names in native SQL queries. For example, both of the following CQL queries are equivalent and will work as expected:
+> [!tip] You may use slugified names in CAP Node.js


Suggested change

> [!tip] You may use slugified names in CAP Node.js

> [!tip] You may use studified names in CAP Node.js

Or maybe one of these: slugged, slugify, sluiced, slugabed?

github-actions · 2026-01-27T09:36:45Z

guides/databases/cdl-to-ddl.md

-> [!tip] Guaranteed & Stable Slugification
-> The slugification effects are guaranteed and stable, which means that you can rely on it and use the slugified names in native SQL queries. For example, both of the following CQL queries are equivalent and will work as expected:
+> [!tip] You may use slugified names in CAP Node.js
+> In CAP Node.js, the slugification effects are guaranteed and stable, which means that you can rely on it and use the slugified names in _native SQL_ queries. For example, both of the following CQL queries are equivalent and will work as expected:


Suggested change

> In CAP Node.js, the slugification effects are guaranteed and stable, which means that you can rely on it and use the slugified names in _native SQL_ queries. For example, both of the following CQL queries are equivalent and will work as expected:

> In CAP Node.js, the specification effects are guaranteed and stable, which means that you can rely on it and use the slugified names in _native SQL_ queries. For example, both of the following CQL queries are equivalent and will work as expected:

Or maybe one of these: ?

github-actions · 2026-01-27T09:36:45Z

guides/databases/cdl-to-ddl.md

-> [!tip] Guaranteed & Stable Slugification
-> The slugification effects are guaranteed and stable, which means that you can rely on it and use the slugified names in native SQL queries. For example, both of the following CQL queries are equivalent and will work as expected:
+> [!tip] You may use slugified names in CAP Node.js
+> In CAP Node.js, the slugification effects are guaranteed and stable, which means that you can rely on it and use the slugified names in _native SQL_ queries. For example, both of the following CQL queries are equivalent and will work as expected:


Suggested change

> In CAP Node.js, the slugification effects are guaranteed and stable, which means that you can rely on it and use the slugified names in _native SQL_ queries. For example, both of the following CQL queries are equivalent and will work as expected:

> In CAP Node.js, the slugification effects are guaranteed and stable, which means that you can rely on it and use the studified names in _native SQL_ queries. For example, both of the following CQL queries are equivalent and will work as expected:

Or maybe one of these: slugged, slugify, sluiced, slugabed?

github-actions · 2026-01-27T09:36:45Z

guides/databases/cdl-to-ddl.md

-await cds.run `SELECT from sap.capire.bookshop.Books`
-await cds.run `SELECT from sap_capire_bookshop_Books`
-```
+> [!warning] Don't use slugified names in CAP Java


Suggested change

> [!warning] Don't use slugified names in CAP Java

> [!warning] Don't use studified names in CAP Java

Or maybe one of these: slugged, slugify, sluiced, slugabed?

github-actions · 2026-01-27T09:36:45Z

guides/databases/cdl-to-ddl.md

-await cds.run `SELECT from sap_capire_bookshop_Books`
-```
+> [!warning] Don't use slugified names in CAP Java
+In CAP Java, you can use fully qualified entity names with dots. The slugified names can't be used in CQL queries.


Suggested change

In CAP Java, you can use fully qualified entity names with dots. The slugified names can't be used in CQL queries.

In CAP Java, you can use fully qualified entity names with dots. The studified names can't be used in CQL queries.

Or maybe one of these: slugged, slugify, sluiced, slugabed?

guides/databases/cdl-to-ddl.md

guides/databases/index.md

Co-authored-by: Matthias Schur <107557548+MattSchur@users.noreply.github.com>

renejeglinsky · 2026-02-03T19:24:43Z

Please resolve the conflicts.

…Functions

agoerler added 2 commits January 20, 2026 21:09

review CAP Java

459586d

Merge remote-tracking branch 'origin/main' into standardFunctions

10986c8

agoerler requested a review from renejeglinsky as a code owner January 20, 2026 20:13

agoerler requested review from MattSchur, danjoa and patricebender January 20, 2026 20:13

agoerler commented Jan 20, 2026

View reviewed changes

guides/databases/cdl-to-ddl.md Outdated Show resolved Hide resolved

agoerler added 3 commits January 20, 2026 21:17

Update guides/databases/cdl-to-ddl.md

2de4a7a

use profiles with cds deploy --dry

e5e563f

Merge remote-tracking branch 'origin/main' into standardFunctions

ec4b149

patricebender approved these changes Jan 23, 2026

View reviewed changes

agoerler commented Jan 23, 2026

View reviewed changes

agoerler and others added 3 commits January 23, 2026 22:38

Apply suggestions from code review

0cfc89d

Co-authored-by: Patrice Bender <patrice.bender@sap.com>

Merge branch 'main' into standardFunctions

8245fd0

Merge branch 'main' into standardFunctions

c2117ce

github-actions bot reviewed Jan 27, 2026

View reviewed changes

agoerler and others added 2 commits January 27, 2026 12:55

review java

ab723b4

Merge branch 'main' into standardFunctions

7b77377

MattSchur reviewed Jan 29, 2026

View reviewed changes

guides/databases/cdl-to-ddl.md Outdated Show resolved Hide resolved

MattSchur reviewed Jan 29, 2026

View reviewed changes

guides/databases/index.md Outdated Show resolved Hide resolved

MattSchur approved these changes Jan 29, 2026

View reviewed changes

BraunMatthias added the merge before release label Jan 29, 2026

Apply suggestions from code review

358eeb8

Co-authored-by: Matthias Schur <107557548+MattSchur@users.noreply.github.com>

agoerler added 4 commits February 4, 2026 11:55

Merge remote-tracking branch 'origin/standardFunctions' into standard…

24c4808

…Functions

Merge remote-tracking branch 'origin/main' into standardFunctions

41f6a44

Merge branch 'main' into standardFunctions

e3eb935

Merge branch 'main' into standardFunctions

fb3242f

	> [!tip] You may use slugified names in CAP Node.js
	> [!tip] You may use studified names in CAP Node.js

	> In CAP Node.js, the slugification effects are guaranteed and stable, which means that you can rely on it and use the slugified names in _native SQL_ queries. For example, both of the following CQL queries are equivalent and will work as expected:
	> In CAP Node.js, the specification effects are guaranteed and stable, which means that you can rely on it and use the slugified names in _native SQL_ queries. For example, both of the following CQL queries are equivalent and will work as expected:

	> [!warning] Don't use slugified names in CAP Java
	> [!warning] Don't use studified names in CAP Java

	In CAP Java, you can use fully qualified entity names with dots. The slugified names can't be used in CQL queries.
	In CAP Java, you can use fully qualified entity names with dots. The studified names can't be used in CQL queries.

Conversation

agoerler commented Jan 20, 2026

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

github-actions bot left a comment

Choose a reason for hiding this comment

Spelling Mistakes

Uh oh!

github-actions bot Jan 27, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot Jan 27, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot Jan 27, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot Jan 27, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot Jan 27, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

renejeglinsky commented Feb 3, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants