Thom Wright

How have other libraries solved this? I expect other libraries read files in similar ways and have had the same problem. I'm open to solutions, but I don't have much...

>You could try e.g. path.join(process.cwd()) from https://github.com/evanw/esbuild/issues/859#issuecomment-790868963 I would be surprised if that worked in a normal Node.js/NPM environment. Perhaps you would like to try it? I see you're also...

Thanks for this, it looks good and I'd like to consider merging it. Before I do, I'd like to think about alternatives, and consider any downsides to this implementation. My...

> > I think an alternative would be to explicitly use the public schema, and potentially allow users to override it. Again, I think this wouldn't break anything. I think...

Hi @mbyrne00, thanks for your interest in moving this PR forwards! I _think_ the main thing is tests. I'm _pretty_ sure this change is backwards compatible, but ideally I'd like...

Thanks for the issue. At the moment, no, there isn't a way. There are a bunch of issues and PRs about similar issues to do with the schema and problems...

Hi, thanks for the issue. I reckon the solution of putting the `err.position` in our error message is something I'd accept a PR for. Probably the main reason I don't...

I don't think Postgres gives that information (correct me if I'm wrong). We can only report what we get back from Postgres. Again, I'm happy to accept a PR for...

Thanks for the suggestion. My initial reaction is, yes I'm hesitant to include due to scope creep! That isn't to say I couldn't be persuaded, but I would need to...

Thanks, I see where you're coming from and that makes sense. I think I like the idea! TBH I'm _probably_ not going to get around to it any time soon,...