I think just specifying the variable as varchar worked. So making sure that the string that I was passing into HoneySQL had "foo AS VARCHAR(40)" attached

oh, nvm. What I said didn't work. What you said is correct. I need to specify it at the driver level. Is there a way to do it with the clojure.java.jdbc driver?

@dbernal The driver will "do the right thing". Can you explain why you think you need to tell the driver to do something different for some particular column?

If the DB column is nvarchar, the value should be inserted/updated as that type of value automatically.

clojure.java.jdbc is not a "driver" by the way, it is a wrapper for whatever JDBC driver you are using.

yea, sorry. I'm using the jtds driver not clojure.java.jdbc

my query is declaring an nvarchar when the underlying DB value is varchar which is creating some performance issues when doing the conversion. So I need to ensure that the input variables into my query are declared as varchar

If I understand correctly what you're saying the driver should understand that the column is varchar and therefore declares the variable as varchar?

@dbernal I'm not sure what you mean by "my query is declaring an nvarchar" -- queries don't "declare" types...

Can you provide some more concrete context for this? Share some code?

clojure.java.jdbc and next.jdbc don't do anything with types -- they just pass everything through to the driver (as Object, essentially) and leave it up to the driver to perform any coercion necessary.

so something like this

DECLARE @P0 BIGINT,
 @P1 BIGINT,
 @P53 NVARCHAR(4000), -- VARCHAR
 @P54 BIGINT,
 @P55 BIGINT,
 @P56 BIGINT,
 @P57 BIGINT,
 @P58 NVARCHAR(4000),  -- VARCHAR
 @P59 BIGINT,
 @P60 NVARCHAR(4000), -- VARCHAR
 @P61 NVARCHAR(4000), -- VARCHAR
 @P62 NVARCHAR(4000), -- VARCHAR
 @P63 NVARCHAR(4000), -- VARCHAR
 @P64 BIGINT,
 @P65 BIGINT

@dbernal Is that SQL something to do with stored procedures? I've never used DECLARE...

I'm using SQL Server. Maybe that's why. That's the underlying query that gets made

Interesting... Have you tried the official MS driver, just to see if the behavior is the same?

(now that it's available as a regular dependency on Maven!)

oh interesting, I have not tried that yet. I'll give that a go!