David Phillips

> We also have a reported issue where outer limits fail to resolve, which may or may not be related > > ```sql > dolt_db> with recursive a as (select...

I am currently encountering what appears to be the same issue using dolt 0.40.0. I am running a nodejs dev app that connects to the dolt sql-server using knex with...

From the above discussion, it sounds like this might be resolved by disabling autocommit. This presumably would bring some implications in how our code is structured - ie needing to...

I have tried disabling autocommit on the connection session and then wrapping the merge action in a knex transaction. The merge is occurring and producing the same message about a...

Wrapping this up, with insights provided above I have been able to resolve this by: 1) disabling autocommit prior to doing the merge 2) start a transaction 3) perform the...

I deleted the db ("mydb") folder, recreated it, reinitialized a new db inside it with: `DOLT_DEFAULT_BIN_FORMAT=__DOLT_1__ dolt init` and the cli appears to be working normally again from ~/dolt. So...

I believe this is related to an issue I'm seeing. On a db that was intended to be a read replica, I ran the following without issue: `dolt sql -q...

I deleted and re-cloned the repo, and then set the vars in the "proper" order (`dolt_replicate_all_heads`, _then_ `dolt_read_replica_remote`) and there were no issues this time.

I am encountering this as well when trying to connect my Agent to a remote server (in my case, Asana's official remote mcp server, though I am assuming the issue...

> > Can you past that example for ease of testing? > > import type { JsonSchemaToTsProvider } from '@fastify/type-provider-json-schema-to-ts'; > import fastify from 'fastify'; > > const server =...