Fork me on GitHub
#sql
<
2019-11-10
>
Darrell00:11:07

@seancorfield I honestly don’t know. This is all new code for me. I’m going to have to go back to the client who wrote it all because none of this makes any sense to me. If I restart everything the test passes but then if I recompile that file and run the test again it fails, without my ever having touched anything. Really frustrating.

seancorfield00:11:20

@darrell And because it's work code, you can't share it I guess?

Darrell00:11:07

Thanks for trying though!

valerauko05:11:42

i think the problem is that you removed all references to it from the source code, but the table schema still has it. so when you try to insert without that field, it defaults to null and errors on you.

valerauko05:11:48

i'd check my db migrations and how it's initialized for testing (since it works if "restarted")

didibus06:11:26

You can't not have a value to a sql column. Even if you remove references to it in the code, trying to insert a row without providing a non null value for that column would cause this.

didibus06:11:39

Also, what do you mean by recompiling and restarting? Can you be more precise?

seancorfield21:11:33

@janne.sauvala The reason it's the default behavior is to fit in more with the trend for using namespace-qualified keywords. So I recommend folks go with that.

seancorfield21:11:33

@janne.sauvala The reason it's the default behavior is to fit in more with the trend for using namespace-qualified keywords. So I recommend folks go with that.

seancorfield22:11:00

@janne.sauvala I've updated the Getting Started docs with an example of options and, specifically, the unqualified lowercase builder. https://github.com/seancorfield/next-jdbc/blob/master/doc/getting-started.md#options--result-set-builders