It's the Aster nCluster driver. Which... is the same as the postgres
driver, theoretically.
However, since it is closed source, I don't know how old the version
of the postgres JDBC it's based on is.
I tried setting DB.quote_identifiers = FALSE, which solved this
particular problem, but still ran into other issues with column names.
I ended up scrapping this particular code and using a different
approach for loading data into these tables.

On Mon, Aug 9, 2010 at 6:54 PM, Jeremy Evans <[email protected]> wrote:
> On Aug 9, 1:10 pm, Rolf Hanson <[email protected]> wrote:
>> http://pastie.org/1082451
>>
>> I've made a pastie which demonstrates the behavior I'm seeing.
>>
>> I realize overriding quote_table_schema is a bad idea, but I just need
>> to figure out how to get this to work, then can fix it later.
>>
>> I've overridden it, as you can see in the pastie. But... something
>> like quote_schema_table still seems to be happening in the insert.
>> Any idea where to look?
>
> On the 3rd line of that pastie: require 'lib/jdbc/noarch-ncluster-jdbc-
> driver.jar'
>
> I'm guessing that driver doesn't support it.  That's not the
> postgresql JDBC driver, which is probably why you are having
> problems.  Your options:
>
> 1) Fix the noarch-ncluster-jdbc-driver
> 2) Use the PostgreSQL JDBC driver
> 3) Try setting DB.quote_identifiers = false
> 4) Don't use schemas in your code
>
> Jeremy
>
> --
> You received this message because you are subscribed to the Google Groups 
> "sequel-talk" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to 
> [email protected].
> For more options, visit this group at 
> http://groups.google.com/group/sequel-talk?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sequel-talk" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sequel-talk?hl=en.

Reply via email to