Skip to content

Releases

v1.1.0

Choose a tag to compare

@github-actions github-actions released this 14 Sep 03:43

Oracle, and views that know whether they can be written to.

Oracle Database

The fifth engine, and the first to need a change to the generator rather than only a provider and a profile. Oracle returns a generated key through an output bind variable — neither a result set nor a second statement in the batch:

INSERT INTO "CCR"."MEMBER" ( ... ) VALUES ( :p_last_name, ... )
RETURNING "MEMBER_ID" INTO :p_generated_key

Three things behave differently there, and the README covers them properly:

  • The Database field is a service name, not a schema — FREEPDB1 on Oracle Free. Getting it wrong produces ORA-50201, whose message blames the syntax of a connect string that is perfectly well-formed. The tool adds its own explanation rather than passing that along unhelped.
  • The left rail lists schemas, and selecting one filters the relation list instead of reconnecting.
  • Identifiers fold to upper case unless they were quoted, and one NUMBER type covers booleans, four integer widths and decimals.

Views are read-only when the database says so

A class generated from a view now only gets Add, Update and Delete when writes through it are actually possible. Previously they were always emitted, with a warning in a UI panel that did not travel with the file.

Engine How it is determined
PostgreSQL information_schema.views.is_updatable, plus is_trigger_updatable
MySQL / MariaDB information_schema.views.is_updatable
Oracle all_updatable_columns — per column, and accurate
SQLite Read-only unless an INSTEAD OF trigger stands in
SQL Server Its IS_UPDATABLE reports NO for views that accept an UPDATE, so it is not read. A trigger proves updatability; otherwise unknown

Unknown stays generous — the methods are still generated and the doubt is recorded — because removing capability on a guess would be worse than the problem. A three-state tick on the Generate tab overrules the database either way.

Fixed

  • MySQL DEFAULT CURRENT_TIMESTAMP columns were being dropped from every INSERT and UPDATE. MySQL reports DEFAULT_GENERATED in a column's extra for any default expression, and the check matched the substring generated, so every created_at and updated_at column was treated as computed. There was no way to set them and nothing said so.
  • Selecting an Oracle schema corrupted the connection string, writing the schema into the service-name slot. The failure looked like a syntax error and could not be recovered from the UI.
  • A ~ in the SQLite database path was not expanded, so ~/data/app.db reached SQLite as a relative path and failed with "unable to open database file" and no path in the message. There is also a Browse… button now.
  • A newly generated class opens at its first line rather than keeping the previous scroll position.

Verification

The live tests — which compile a generated class with Roslyn and drive real CRUD through it — now run in CI against all five engines, using service containers. On an amd64 runner that includes the genuine SQL Server image.

Downloads

Self-contained single executables. No .NET runtime to install.

x64 arm64
Linux CCReimagined-1.1.0-linux-x64.tar.gz CCReimagined-1.1.0-linux-arm64.tar.gz
Windows CCReimagined-1.1.0-win-x64.zip CCReimagined-1.1.0-win-arm64.zip
macOS CCReimagined-1.1.0-osx-x64.tar.gz CCReimagined-1.1.0-osx-arm64.tar.gz

Extract and run. On macOS, Gatekeeper needs xattr -d com.apple.quarantine CCReimagined.App — the binaries are not signed or notarised.

Upgrading from 1.0.0

Regenerating a class from a view may remove Add, Update and Delete where the database reports the view as read-only. That is the point of the change, but it is a difference in generated output rather than only an addition — check any view-derived class before replacing it.

Full Changelog: v1.0.0...v1.1.0

v1.0.0

Choose a tag to compare

@github-actions github-actions released this 13 Sep 17:38

The CodeComplete data-class generator, rebuilt as a cross-platform Avalonia app — and no longer tied to SQL Server.

Point it at a table or view and it writes the same data-abstraction class the original did: a property per column, then Initialize, CopyFields, RecExists, Add, Update, Delete, Read, ReadAsDataTable, GetAll, and a GetListBy… for every column you pick. That class has the same members, names and signatures whatever database it came from.

Four engines

Engine Browsing Generated code uses
Microsoft SQL Server sys.objects, sys.columns Microsoft.Data.SqlClient
PostgreSQL information_schema, pg_database Npgsql
MySQL / MariaDB information_schema MySqlConnector
SQLite sqlite_master, PRAGMA table_xinfo Microsoft.Data.Sqlite

Four things adapt per engine and nothing else: the client library, the parameter DbType enum, identifier quoting, and how a generated key comes back — SCOPE_IDENTITY(), RETURNING, LAST_INSERT_ID(), last_insert_rowid().

Browsing and emitting are independent choices, so a SQL Server schema can produce an Npgsql class. That is what porting a table between engines needs.

Downloads

Self-contained single executables. No .NET runtime to install.

x64 arm64
Linux CCReimagined-1.0.0-linux-x64.tar.gz CCReimagined-1.0.0-linux-arm64.tar.gz
Windows CCReimagined-1.0.0-win-x64.zip CCReimagined-1.0.0-win-arm64.zip
macOS CCReimagined-1.0.0-osx-x64.tar.gz CCReimagined-1.0.0-osx-arm64.tar.gz

Extract and run. On macOS, Gatekeeper will need xattr -d com.apple.quarantine CCReimagined.App — the binaries are not signed or notarised.

Start here

docs/CCReimagined-Developer-Guide.pdf — seven pages, with the generated output for the same table set side by side across all four engines.

dev/sample-databases has a Docker Compose stack and a schema built to exercise the awkward cases, if you want something to point it at.

Moving from the old generated classes

Some behaviours were corrected rather than carried across:

  • Nullable columns are nullable properties. The old classes used sentinels ("", a minimum date), so "not set" and "legitimately empty" were indistinguishable. Binding an empty string as NULL is still available as an opt-in.
  • Reserved words match exactly. The original tested whether a name contained a keyword, so INTERVIEWER was renamed because it contains int.
  • Columns follow the table's declared order, not alphabetical.
  • Identity detection covers serial, AUTO_INCREMENT and SQLite's rowid alias, not just IDENTITY.
  • A table with no auto-numbering key still generates — the assumption is shown and the key is a checkbox you can move. The original stopped at a modal dialog.
  • ReadAsDataSet became ReadAsDataTableAsync, because not every provider ships a DataAdapter.
  • Async throughout, with blocking wrappers kept for callers that cannot await.

How far it is verified

For each engine the suite creates a table, discovers it, generates the class, compiles that class with Roslyn, and drives insert, key read-back, read, update, exists, both list getters and delete against a real server. Generated code that does not build, or does not round-trip a row, fails the build.

Not carried over yet

The XAML, WinForms, HTML/CSS, JavaScript and TypeScript generators, the LM Studio integration and the subnet scanner. This release is the database orchestration.


Requires the .NET 10 SDK only if you build from source. Pinned to Avalonia 11.3 because the generated-code editor uses SyntaxColorizer.