Pete wrote: > I am aware that if you enclose those table and column names with " > then postgresql will take the case into consideration. Only problem > is most people who have current MySQL project have not written their > statements with " (MySQL parser uses no quotes of the ` back tick) > and it would take considerable man power to convert each SQL > statement.
Why would this be a problem, considering that all uses of the same mixed-case identifier are converted to the same lower-case identifier? ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
