After the fix, I'm having a different problem now with latest 1.1-SNAPSHOT
(10/30 1:54:48PM build) with tables in the DB that have uppercase anywhere
in either the dbTableName or dbColumnName name... the Mapper is creating SQL
that throws exceptions due to unknown column in MySQL (which is case
I'm going to revert the fix.
I'm going to add tests for mixed-case column and table names. If you care
to donate some of these tests, that'd be great.
Please open a ticket.
On Sat, Oct 31, 2009 at 5:35 AM, Troy Noble econop...@gmail.com wrote:
After the fix, I'm having a different problem
Thanks for your support... and I'm very sorry to be the instigator of the
breakage. I feel really bad that everything broke for all the MySQL and SQL
server users (I gotta believe I'm not the only freak still using MySQL or
SQL Server ;-)
The only way to INTEGRATION test right now would be to
David,
I opened ticket # 151. And I have some test cases written for uppercase
dbTableName and dbColumnName. They are very simple-minded re-use of the Dog
mapped class, but they do demostrate the same sort of failure behavior I was
seeing in 1.1-SNAPSHOT, this time against the pre-145-fix
On Thu, Oct 29, 2009 at 10:15 PM, Troy Noble econop...@gmail.com wrote:
We are using Mapper with a legacy database with many columns that we
are not allowed to rename in our database. For example CREATE_DATE
for which we created the following seemingly simple mapped field in
our model:
Certainly. I will open a ticket. I might have found 3 different issues...
(one each for Mapper, schemify, CRUDify) all related to dbColumnName (see
details below).
I created a new scaled down project against 1.1-SNAPSHOT and an embedded
Derby database, and it exhibits the Mapper dbColumnName
I have seen EXACTLY same behavior when dbColumnName returned _upcased_ names
lopex
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Lift group.
To post to this group, send email to liftweb@googlegroups.com
To
Turns out this was the problem. Some RDBMSs are case insensitive on
table/column names... others are not.
I committed a fix (now on master thanks to fast review board turn-around)
that causes all table and column names to lower case for all SQL
transactions.
2009/10/30 Marcin Mielżyński
Thanks. I'll give it try. Dumb newbie question though... how do I access
the update? Git + build from github, or can I just grab the latest
1.1-SNAPSHOT?
Thanks again, Troy
On Fri, Oct 30, 2009 at 3:01 PM, David Pollak feeder.of.the.be...@gmail.com
wrote:
Turns out this was the problem.
On Fri, Oct 30, 2009 at 3:06 PM, Troy Noble econop...@gmail.com wrote:
Thanks. I'll give it try. Dumb newbie question though... how do I access
the update? Git + build from github, or can I just grab the latest
1.1-SNAPSHOT?
Check http://hudson.scala-tools.org/job/Lift/
You can see if the
10 matches
Mail list logo
