Skip to content

Conversation

@renejeglinsky
Copy link
Contributor

@danjoa Some edits by AI that I wanted to get a review on.


Clarified CQL behavior regarding != operator and its translation in SQL databases. Updated note on database-specific behavior for portable functions.

Clarified CQL behavior regarding != operator and its translation in SQL databases. Updated note on database-specific behavior for portable functions.
@renejeglinsky renejeglinsky requested a review from danjoa January 29, 2026 09:11
Comment on lines +84 to +98
## Data Loading Order

CAP loads CSV files in **alphabetical order by filename**. When tables have foreign key relationships, ensure parent tables load before child tables to avoid constraint violations.

**Example:**
```
db/data/
├── sap.capire.bookshop-Authors.csv # Loads first (parent)
└── sap.capire.bookshop-Books.csv # Loads second (references Authors)
```

The filename prefix ensures correct order: `Authors` loads before `Books` alphabetically. If you encounter foreign key violations, verify your file naming follows dependency order.

> [!tip] Large Datasets
> For datasets with thousands of rows, consider using database-specific bulk loading tools instead of CSV files. The CSV mechanism loads all data in a single transaction, which can cause memory issues and long startup times.
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Another proposal by AI. I don't think that this is true, but how is the actual behavior?

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