Lyle Johnson

I just ran into this. Same problem as reported by @icymind and @samdammers: the contents of my (local) `index.html` file had changed, but its file size was the same as...

Yes, we're running a local SurrealDB instance (with authentication enabled) in a Docker container. With `@sebastianwessel/surql-gen` version 1.1.3, values of "ws://127.0.0.1:8000" and "ws://127.0.0.1:8000/rpc" work now for the "surreal" parameter in...

I've been advised by some others on the Discord that if the edge table had been defined as `SCHEMALESS` this would have worked as documented. So maybe a disclaimer along...

Figured it out (sort of): It's not processing the query bindings properly. If I change the `query` call from this: ``` const modelSchemaIds = ['model_schema:x']; const response = await this.query('SELECT...

Also works if I map them to `StringRecordId` instances: ``` const modelSchemaIds = ['model_schema:x']; const response = await this.query( 'SELECT VALUE

I removed the migrations from the equation and now it can't even apply the schemas. Going to try turning it off and turning it on again.

Here's the stack trace I obtained by running with `RUST_BACKTRACE=full` and `COLORBT_SHOW_HIDDEN=1`: ``` Error: 0: There was an error processing a remote HTTP request: HTTP status client error (413 Payload...

Looks like it's concatenating all of the schema files into one big blob? ``` fn extract_schema_definitions(schemas_files: Vec) -> String { concat_files_content(schemas_files) } ``` So that's surely the problem. I'm sure...

> I think the reason it's done this way is because SurealDB does not currently support cross-request transactions. So, in order to apply a migration, it tries to do it...