Oh, no trouble at all. I just merge whenever I update. I haven't submitted a patch because I didn't want to push a design change for something that is not too common (camel case table and column names).
The patch is a just a few lines of code. I'll take a look at see if it is fit for general use. Thanks, McKinley On Mon, Feb 8, 2010 at 6:44 AM, Francis De Brabandere <[email protected]>wrote: > Patches are welcome ;-)... and I must have caused you some trouble with all > my changes? > > Thanks > > > On Mon, Feb 8, 2010 at 1:52 AM, McKinley <[email protected]> wrote: > >> For what it is worth, in Empire-db I maintain a personal patch during all >> updates that turns upper case off. I use the straight table and column names >> in codegen too and I apply quoted identifiers for the string name on each. >> >> Thanks, >> >> McKinley >> >> >> On Sun, Feb 7, 2010 at 11:38 PM, Francis De Brabandere < >> [email protected]> wrote: >> >>> Rainer? >>> >>> On Sun, Jan 10, 2010 at 7:43 PM, Exxos <[email protected]> wrote: >>> >>>> Hi, >>>> >>>> db.album.title.as("title") will generates the following SQL column name >>>> >>> "TITLE" in upper case in the SQL command... >>>> >>>> Is there any reason? >>>> >>>> cmdUnion.select(db.album.id >>>> ,db.album.title,db.album.index,db.album.serieId,db.album.title.as >>>> ("title")); >>>> SELECT t1.alb_id, t1.alb_title, t1.alb_index, t1.alb_ser_id, >>>> t1.alb_title AS TITLE >>>> >>>> This is not consistent in case of using lower case for defining columns >>>> name and this is too intrusive... I think this is the responsability of the >>>> developper and not empire-db to decide. >>>> >>>> Please advise. >>>> >>>> /Cheers >>>> >>>> >>> >>> >>> -- >>> http://www.somatik.be >>> Microsoft gives you windows, Linux gives you the whole house. >>> >> >> > > > -- > http://www.somatik.be > Microsoft gives you windows, Linux gives you the whole house. >
