Skip to content

Feature/sqlite compiletime#1180

Open
Donach wants to merge 1 commit into
wurstscript:masterfrom
Code-Fixxers:feature/sqlite-compiletime
Open

Feature/sqlite compiletime#1180
Donach wants to merge 1 commit into
wurstscript:masterfrom
Code-Fixxers:feature/sqlite-compiletime

Conversation

@Donach

@Donach Donach commented Apr 3, 2026

Copy link
Copy Markdown
Contributor

This PR adds compiletime support for sqlite operations. Not thoroughly tested, but simple stuff works:

Self-contained Examples:
SQLite.txt
SQLiteHelder.txt

@Frotty

Frotty commented Jun 6, 2026

Copy link
Copy Markdown
Member

Hi, as mentioned, will you do the standard library pendant? (provide api functions) else this isn't publicly usable unless users define @extern natives by themselves?

@Donach

Donach commented Jul 22, 2026

Copy link
Copy Markdown
Contributor Author

Updated this PR with the clean implementation (including handle validation, statement connection ownership tracking, auto-finalizing open statements when closing connections, and explicit interpreter error messages).

Also opened the WurstStdlib2 PR providing the native @extern bindings: wurstscript/WurstStdlib2#450

@Frotty

Frotty commented Jul 22, 2026

Copy link
Copy Markdown
Member

@codex review

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1742a4fbd7

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@Donach
Donach force-pushed the feature/sqlite-compiletime branch 3 times, most recently from d03161c to 5d16740 Compare July 22, 2026 22:23
@Donach
Donach force-pushed the feature/sqlite-compiletime branch from 5d16740 to 6e51eb3 Compare July 22, 2026 22:27
@Frotty

Frotty commented Jul 23, 2026

Copy link
Copy Markdown
Member

@codex review

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6e51eb3786

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

ResultSet rs = sqliteResultSets.remove(statement.getVal());
if (rs != null) rs.close();
sqliteExecutedStatements.remove(statement.getVal());
stmt.clearParameters();

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Preserve SQLite bindings across reset

When a prepared statement with bound parameters is reset and stepped again without rebinding every parameter, this line clears all JDBC bindings. SQLite's reset operation leaves bindings in place, so common reuse patterns like binding a WHERE parameter once, reading a row, calling sqlite_reset(stmt), and stepping again silently query with NULL/no values or fail constraints instead of reusing the previous values. Please reset execution state without clearing bindings; expose a separate clear-bindings operation if needed.

Useful? React with 👍 / 👎.

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