Neil Macneale IV
Neil Macneale IV
Not clear where the historical information is dumped to. Some design required here.
Also, doesn't seem to effect the stored procedure. ``` db5/main> call dolt_commit("--allow-empty","-m", "commit again"); +----------------------------------+ | hash | +----------------------------------+ | fsqui9k22g6nhdlr41hga5niobh0ov6v | +----------------------------------+ 1 row in set (0.01 sec) db5/main>...
Filling in some blanks here. * Clone a repository from dolthub.com that you have write access too. * Run a local server: `dolt sql-server` * In the same directory, run...
I've gone over this a couple times, and verified that this is working as designed. The `dolt_branches` table should only show local branches, not remote branches. Resolving.
Hey @GodGavin! Thanks for the contribution! After discussing with the team, we believe that this approach is not correct. Using a stored procedure which takes a SQL string is not...
A possible better first step would be: https://github.com/dolthub/dolt/issues/8875
No, I think the approach doesn't fit with the way the application works. For example 'os.Args[1:]' should definitely not be used anywhere close to the sql engine. There are many...
I'm going to close this PR since it's gone dormant.