Hi Alex, I dont have the authority to speak on behalf of Phoenix Committers. However, in worst case, if your contribution is not accepted by Phoenix, then also you can locally patch Phoenix and use it the way you want. Many people use open source softwares like that.
HTH, Anil On Fri, Jun 19, 2015 at 8:07 AM, Alex Bedley <aeoli...@gmail.com> wrote: > Hey James, > > Thanks for the suggestions. Unfortunately Microsoft Query automatically > prepends the table name to all the columns so having an implicit column > family will not work. I was wondering if you think the Phoenix community > would accept a contribution to have a config setting to turn off auto > uppercase? > > Thanks again, > > - Alex > > On Thu, Jun 18, 2015 at 4:57 PM, James Taylor <jamestay...@apache.org> > wrote: > >> Hi Alex, >> We don't have a way of globally enabling/disabling the normalization >> we do for column names by uppercasing them. However, there are a >> couple of feature that might help you: >> 1) You don't need to reference column family names unless column names >> are ambiguous without it. >> 2) You can set a "default" column family name on the table when you >> create it like this: >> CREATE TABLE my_table (k integer primary key, v integer) >> default_column_family='a'; >> In this case the column family for columns outside your primary key >> constraint will be in that default column family name instead of our >> default column family name (which is 0). >> HTH. Thanks, >> James >> >> >> On Thu, Jun 18, 2015 at 10:10 AM, Alex Bedley <aeoli...@gmail.com> wrote: >> > Hello, >> > >> > I'm trying to access Phoenix using Microsoft Excel. I have written a >> very >> > thin ODBC wrapper around Phoenix that I use to pass SQL from Microsoft >> Query >> > to my ODBC (which just passes the SQL along) to Phoenix. >> > >> > My problem is with case-insensitivity. All my column >> families/qualifiers are >> > lowercase. I know I can just surround them with double quotes in my SQL >> > statement and Phoenix will not auto-uppercase them. Unfortunately, I >> can't >> > control exactly what Microsoft Query sends along to my ODBC. >> > >> > For example, if I have a column family of "a" and a column qualifier of >> "b" >> > >> > Microsoft Query will send: "a.b" >> > When I really want: "a"."b" >> > >> > I have tried aliasing the column "a"."b" to A.B but as I understand it, >> > Phoenix does not support aliasing in CREATE VIEW or CREATE TABLE. >> > >> > Is there a config setting in Phoenix that I can set to turn off >> > auto-uppercase? If this setting does not exist, is this something I >> could >> > contribute to the project? I understand I can modify my schema to be all >> > uppercase or I could parse the SQL and fix it in my ODBC but I'm >> wondering >> > if there is a Phoenix solution to this problem. >> > >> > Thank you for your time, >> > >> > - Alex >> > > -- Thanks & Regards, Anil Gupta
