Mr-Dispatch
Mr-Dispatch
+1, if creation of tables / migration is supported, foreign keys should be supported, especially for ON UPDATE / ON DELETE support (it is quite a bit of error-prone work...
I agree that it [":extra-sql"-like mechanism] would be a nice addition, but IMO foreign keys and [potentially multi-field] indexes & constraints should be supported out of the box (as a...
@eko234 Well, Mito's claim is "Supports MySQL, PostgreSQL and SQLite3". SQLite3 even doesn't enforce foreign keys (AFAIR) unless forced by a PRAGMA. But it still supports them on the "declaration...
Fugly work-around is to deftable the same table twice (first time with no fields). It didn't even occur to me this is not supported, and as I built-up my prototype...
I recommend closing this, the difference between :references (just create a column for ID from another table) and :col-type table_type (same column, but added machinery for querying referenced objects) seems...
I'd add here that I'd like to see a "query POST variant" being basically the same as the command variant, but limited to queries / "idempotent commands".
Shit, wrong click, and I can't delete it.
Reopening with new name and relevant link: - https://stackoverflow.com/questions/30829364/open-utf8-encoded-filename-in-c-windows (see the update in accepted answer for a quick summary).
The referenced upstream issue is now stuck on "I'm not a magit user, can someone give me the commands to reproduce it", so if anyone can...
Or at least an error if (diverging) SKIP/LIMIT are present both in the HTTP request and in the query itself.