Disable double underscore behaviour for Sequel

Question

How disable double underscore behaviour for Sequel?

I work with legacy data base schema where I have a lot of columns with "__" in name.

db[:abc].insert({vector_a__c: "356"})
Sequel::DatabaseError: PG::UndefinedColumn: ERROR:  column "vector_a" of relation "abc" does not exist
LINE 1: INSERT INTO "abc" ("vector_a"."c") VALUES ('356') RETURNING ...

Who creates a schema with double-underscores? You sure you can't just rename these tables? — tadman, Mar 30 '15 at 17:01
You can't rename legacy tables or legacy apps accessing them will break. — the Tin Man, Mar 30 '15 at 20:25
I'd ask this on the Sequel IRC or mail lists. Jeremy Evans will be able to tell you exactly where to look. — the Tin Man, Mar 30 '15 at 20:26

score 3 · Accepted Answer · answered Apr 01 '15 at 15:39

In general you want to wrap it in an identifier:

db[:abc].insert(Sequel.identifier(:vector_a__c) => "356")

Using a string as an identifier only works in very few cases for backwards compatibility, where it is unambiguous (i.e. where an SQL string would not be valid).

score 1 · Answer 2 · answered Mar 31 '15 at 10:21

1

Double underscore behavior disabling when you transfer columns names as string but not as symbol.

For example:

db[:abc].insert({"vector_a__c" => "356"})

answered Mar 31 '15 at 10:21

Anton Senik

41
5

Disable double underscore behaviour for Sequel

2 Answers2