I think you've figured it out yourself. You'd have to have a pretty
compelling use case to use a BINARY column for a PK I think. It would be
very inefficient! Unless it is a really small BINARY column.
On 7/03/2013 10:23 PM, Zach wrote:
I have a table with a BINARY column that acts as a primary key. I want
to index this table for searching, but I obviously don't want it to
index this column. When I call "FT_CREATE_INDEX('PUBLIC', 'TEST',
NULL)" on the table, will it ignore the column because it's BINARY, or
will it try indexing it?
I know I can specify a comma-delimited list of columns in the third
parameter. However, since this BINARY column acts as a primary key, I
think I need it in the indexed table so I can properly JOIN it to the
original table.
--
You received this message because you are subscribed to the Google
Groups "H2 Database" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/h2-database?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/h2-database?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
