Database Designer · published · build 25688449
Database Designer 3.0 is about one goal: you should be able to design a real backend (a store with stock and payments, say), export it, and have it actually run. IN SHORT, IT FULLY WORKS AS INTENDED! Almost every error has been fixed (although the theme system was dialed back for now)! This will probably be the last update I make to this thing for a while, specifically moving to the Supporter's Pack! We got around 10k users on Database Designer but I want to treat the 5 who got the Supporter's Pack well! I also plan on creating Frontend Designer, although i'm not sure if that will be in the Supporter's Pack or a completely different thing! It will be able to create full frontends for websites and software using OpenSilver and connect to Database Designer. I only want to make sure I learn a few things though because while i'm fine with AI helping here and there, I do NOT want it to be the main driver of progress. Some of you may know this but I also make VR headsets with my company! https://vectorgear.xyz I am working on a Steam Alternative called WlkrWrks (WalkerWorks) that acts like Steam but for general software! I expect errors to appear here and there but as usual I will handle them as they're noted!
Working API. The exported API now builds and runs. Models come from your tables, every API function with a NodeWalker graph becomes a route, and the graph's inputs become request parameters.
Local Database. Build your tables on your own Postgres, fill them with sample data, try queries, and start the API with Swagger, all from one window.
Migrations. Every build writes a Migration.sql that upgrades a database built from the previous build, without losing data.
Row level security that works. RLS.sql runs cleanly on a real database, and each policy now has a Command, an Access level and an Owner column, plus a line that says in plain words what it allows.
A smarter Build Check. Catches missing primary keys, reserved words, capital letters in column names, mismatched or broken references, reference cycles, bad indexes and RLS policies that can't work.
Flow wires. White pins that decide what runs next, with new Branch, Sequence, For Each, Repeat, Try and Return blocks. Old graphs work as before.
Run a graph against your Local Database and see the result, or the error and the block that caused it.
Comparisons fixed. Equals, Greater Than and the rest compare numbers, number-like text, dates and nulls properly, instead of throwing "Object must be of type Double".
Query blocks replace the old Lambda block: Where: Equals, Greater, Contains, Between, In and many more, plus DB: Query.
List blocks for filtering, sorting, counting and summing lists.
Store blocks: Fail If, Env Var, Set Field, Object: Build, atomic DB: Increment / Decrement Where, HTTP: Post Form and more.
Undo and redo inside NodeWalker.
Graphs from templates are laid out neatly the first time you open them.
ER Diagram with SVG and PNG export.
Import SQL to turn an existing Postgres schema into tables.
Notes inside each project, with pinning, search and checklists.
Foreign key picker: pick the table and column from a list. Only valid targets are shown, and mismatched types are flagged.
Undo and redo for the whole project (Ctrl+Z / Ctrl+Y).
Table templates work. Picking a template pack now adds its tables to your project. The template builder checks your entries as you type.
Simple Store project template: a working store with stock and Stripe payments.
Portable projects. Export a project as a single .ddproject file and import it on any account.
Password recovery. Forgot Password? / Change Password works, using your recovery code or your current password. Accounts made before 3.0 get a recovery code on their next login.
Themes. The Default theme looks the way the app did before themes existed.. Wallpapers fill the screen without stretching, including on ultra-wide monitors.
Music player. Your own songs (from the Music folder) play, keep playing after the player is closed, and the player opens again properly afterwards. Play counts go up when a song finishes, and every time it loops.
Text boxes in Notes, Import SQL and Local Database fill their window and scroll.
Double-clicking a desktop icon opens one window instead of two, and closing a window removes its icon from the lower bar.
Column lengths are kept (varchar(50), numeric(10,2)).
Default values containing an apostrophe work.
Composite primary keys generate valid SQL.
Double Precision and range columns (int4range, daterange and so on) use names Postgres understands.
If you set a length or precision on a column before 3.0, your next build will include it. Check Migration.sql before running it on a live database.
Accounts made before 3.0 are shown a recovery code on their first login. Save it; it's the only way back in if you forget your password.
Templates made with older versions may need exporting again.