The keycloak project ended with four open questions that design could not
settle. A two-VM lab was built to answer them by measurement, and this is
that material: 26 experiments, 125 raw command outputs, 22 browser captures.
Follows the import procedure in README.md.
source/ the originating repository verbatim — 78 documents, 28 SVGs,
8 manifests, plus .source-revision recording the commit
final/ the SSOT
document.md 729 lines written from the 29 experiment documents, not
concatenated: what was predicted, what was measured, and
where the measurement itself was wrong
evidence/raw 125 outputs, flattened to <experiment>__<file> because
the originals collided (01-baseline.txt appeared three
times) and the audit only globs the top level
evidence/meta one per raw file; command and exitCode are null and the
README says why rather than inventing them
evidence/browser 22 captures
assets/ three diagrams through techviz
.techviz/ their VizSpecs
A separate project rather than an addition to keycloak: the B-layer answers
that project's four questions, but the A, C and D layers are about cluster
failure, SSO and operations, and one document.md should hold one subject.
The four question records there can point here through 관계.
Recorded rather than papered over: only three of the 28 diagrams were
remade. The repository forbids hand-drawn SVG and forbids titles inside the
canvas; all 28 originals carry both, so converting them is redrawing, not
reformatting. They stay in source/ and the gap is written into the document.
verify-pipeline.py passes. audit-records.py reports no issues.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
22 lines
933 B
Plaintext
22 lines
933 B
Plaintext
# 락파일이 고정한 제공자
|
|
h2-2.4.240.jar
|
|
hibernate-core-7.2.24.Final.jar
|
|
# 저장소에서 fail_on_pagination_over_collection_fetch 를 켜는 곳: 0
|
|
|
|
# 게이트와 같은 모양의 조회를 그 제공자에게 직접 시킨다
|
|
WARN org.hibernate.orm.query -- HHH90003004: firstResult/maxResults specified with collection fetch; applying in memory
|
|
반환된 부모 수 : 20
|
|
그 조회가 낸 프리페어드 스테이트먼트 : 1
|
|
fail_on_pagination_over_collection_fetch : false
|
|
|
|
# 서버 없이 매 빌드마다 도는 레인에도 같은 형태가 있다
|
|
|
|
@Test
|
|
@DisplayName("one collection page requires a database-level parent bound")
|
|
void oneCollectionPageRequiresBoundedParentSelection() {
|
|
var expected = FetchPaginationExpectation.hibernate74PostgreSql(20);
|
|
|
|
assertThat(expected.maxReturnedParents()).isEqualTo(20);
|
|
assertThat(expected.requiresDatabaseLimit()).isTrue();
|
|
}
|