Re: [Lift] Re: 1.1-M8 to 2.0-M1 behavior change

[David Pollak]

On Thu, Jan 21, 2010 at 1:24 AM, aw  wrote:

> I think I discovered that my issue is related to the fact that the
> code is part of a CometActor/CometListener, and it sounds like S isn't
> fully functional from this perspective...  My clue was the
> inStatefulScope_? method documentation.
>
> I do think I managed to work around my specific issue, but I don't
> fully understand this, and I'm not sure if this change in behavior was
> intentional.
>

There is no HTTP request within the scope of a CometActor.  This is the
defined behavior.  If you were somehow able to access a Req or other part of
an HTTP request within the CometActor scope in a prior version of Lift, this
was a bug.


>
> --
> You received this message because you are subscribed to the Google Groups
> "Lift" group.
> To post to this group, send email to lift...@googlegroups.com.
> To unsubscribe from this group, send email to
> liftweb+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/liftweb?hl=en.
>
>
>
>


-- 
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Surf the harmonics
-- 

You received this message because you are subscribed to the Google Groups "Lift" group.

To post to this group, send email to lift...@googlegroups.com.

To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.

[Lift] Re: 1.1-M8 to 2.0-M1 behavior change

[aw]

I think I discovered that my issue is related to the fact that the
code is part of a CometActor/CometListener, and it sounds like S isn't
fully functional from this perspective...  My clue was the
inStatefulScope_? method documentation.

I do think I managed to work around my specific issue, but I don't
fully understand this, and I'm not sure if this change in behavior was
intentional.
-- 
You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to lift...@googlegroups.com.
To unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en.

[Lift] Re: 1.1: children of menu items do not appear

[Joachim A.]

Tim,
thanks again for the reply.
I did clean out the old code.

In 1.1  I've hit the bug, I think.
I found the reason why it did not work with 2.0. I had to use
expandAll and had to adjust the css for the menu.
It's working fine now.

Thanks guys!
Joachim

On Jan 16, 6:15 pm, Tim Nelson  wrote:
> Did you "clean" out your code before you updated? I don't use maven,
> so I'm not sure of the exact command, but that seems to come up a lot
> on this list.
>
> If you indeed did clean out the code before updating, then I'm afraid
> I'm not sure how to help you further. I've only used mappper a little
> and crudify never.
>
> If you manually put in a menu location, does that work? That should
> narrow down if it's crudify related or not.
>
> Tim
>
> On Sat, Jan 16, 2010 at 10:38 AM, Joachim A.
>
>
>
>  wrote:
> > Tim,
> > thank you for your reply.
> > I've updated updated to 2.0-SNAPSHOT now. The submenu items still do
> > not appear, though.
>
> > Do I need to set some options or is it still the bug you mentioned?
>
> > Regards,
> > Joachim
>
> > On Jan 16, 4:36 pm, Tim Nelson  wrote:
> >> There was a bug that's been fixed. I suggest you use the newest
> >> version, which is 2.0-SNAPSHOT. 1.1 was renamed 2.0 last week.
>
> >> Tim
>
> >> On Sat, Jan 16, 2010 at 6:59 AM, Joachim A.
>
> >>  wrote:
> >> > Hi,
> >> > I've been away from Lift for quite a time. At the moment I work on an old
> >> > project and am in the progress to update to the current 1.1-SNAPSHOT .
> >> > I have to say that getting used to Lift again was very quick and easy.
>
> >> > In 1.0 this worked and showed a top-level menu item and submenu items if
> >> > you've clicked on it:
> >> >        Menu(Loc("admin_newsletter", List("newsletter"), 
> >> > S.?("menu.newsletters"),
> >> > testUserNotSuper), Newsletter.menus: _*) ::
>
> >> > In 1.1 the submenu items do not appear. "Newsletter" uses Crudify.
>
> >> > I've tried  the expandAll attribute for Menu.builder but this did not 
> >> > work.
>
> >> > I'd appreciate some hints where to look,
>
> >> > Best regards,
> >> > Joachim
>
> >> > --
> >> > You received this message because you are subscribed to the Google 
> >> > Groups "Lift" group.
> >> > To post to this group, send email to lift...@googlegroups.com.
> >> > To unsubscribe from this group, send email to 
> >> > liftweb+unsubscr...@googlegroups.com.
> >> > For more options, visit this group 
> >> > athttp://groups.google.com/group/liftweb?hl=en.
>
> > --
> > You received this message because you are subscribed to the Google Groups 
> > "Lift" group.
> > To post to this group, send email to lift...@googlegroups.com.
> > To unsubscribe from this group, send email to 
> > liftweb+unsubscr...@googlegroups.com.
> > For more options, visit this group 
> > athttp://groups.google.com/group/liftweb?hl=en.
-- 
You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to lift...@googlegroups.com.
To unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en.

Re: [Lift] Re: 1.1: children of menu items do not appear

[Timothy Perrett]

Try:

mvn -U clean jetty:run

Cheers, Tim

On 16 Jan 2010, at 17:15, Tim Nelson wrote:

> Did you "clean" out your code before you updated? I don't use maven,
> so I'm not sure of the exact command, but that seems to come up a lot
> on this list.
> 
> If you indeed did clean out the code before updating, then I'm afraid
> I'm not sure how to help you further. I've only used mappper a little
> and crudify never.
> 
> If you manually put in a menu location, does that work? That should
> narrow down if it's crudify related or not.
> 
> Tim
> 
> On Sat, Jan 16, 2010 at 10:38 AM, Joachim A.
>  wrote:
>> Tim,
>> thank you for your reply.
>> I've updated updated to 2.0-SNAPSHOT now. The submenu items still do
>> not appear, though.
>> 
>> Do I need to set some options or is it still the bug you mentioned?
>> 
>> Regards,
>> Joachim
>> 
>> On Jan 16, 4:36 pm, Tim Nelson  wrote:
>>> There was a bug that's been fixed. I suggest you use the newest
>>> version, which is 2.0-SNAPSHOT. 1.1 was renamed 2.0 last week.
>>> 
>>> Tim
>>> 
>>> On Sat, Jan 16, 2010 at 6:59 AM, Joachim A.
>>> 
>>> 
>>> 
>>>  wrote:
 Hi,
 I've been away from Lift for quite a time. At the moment I work on an old
 project and am in the progress to update to the current 1.1-SNAPSHOT .
 I have to say that getting used to Lift again was very quick and easy.
>>> 
 In 1.0 this worked and showed a top-level menu item and submenu items if
 you've clicked on it:
Menu(Loc("admin_newsletter", List("newsletter"), 
 S.?("menu.newsletters"),
 testUserNotSuper), Newsletter.menus: _*) ::
>>> 
 In 1.1 the submenu items do not appear. "Newsletter" uses Crudify.
>>> 
 I've tried  the expandAll attribute for Menu.builder but this did not work.
>>> 
 I'd appreciate some hints where to look,
>>> 
 Best regards,
 Joachim
>>> 
 --
 You received this message because you are subscribed to the Google Groups 
 "Lift" group.
 To post to this group, send email to lift...@googlegroups.com.
 To unsubscribe from this group, send email to 
 liftweb+unsubscr...@googlegroups.com.
 For more options, visit this group 
 athttp://groups.google.com/group/liftweb?hl=en.
>> 
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "Lift" group.
>> To post to this group, send email to lift...@googlegroups.com.
>> To unsubscribe from this group, send email to 
>> liftweb+unsubscr...@googlegroups.com.
>> For more options, visit this group at 
>> http://groups.google.com/group/liftweb?hl=en.
>> 
>> 
>> 
>> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Lift" group.
> To post to this group, send email to lift...@googlegroups.com.
> To unsubscribe from this group, send email to 
> liftweb+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/liftweb?hl=en.
> 
> 

-- 
You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to lift...@googlegroups.com.
To unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en.

Re: [Lift] Re: 1.1: children of menu items do not appear

[Tim Nelson]

Did you "clean" out your code before you updated? I don't use maven,
so I'm not sure of the exact command, but that seems to come up a lot
on this list.

If you indeed did clean out the code before updating, then I'm afraid
I'm not sure how to help you further. I've only used mappper a little
and crudify never.

If you manually put in a menu location, does that work? That should
narrow down if it's crudify related or not.

Tim

On Sat, Jan 16, 2010 at 10:38 AM, Joachim A.
 wrote:
> Tim,
> thank you for your reply.
> I've updated updated to 2.0-SNAPSHOT now. The submenu items still do
> not appear, though.
>
> Do I need to set some options or is it still the bug you mentioned?
>
> Regards,
> Joachim
>
> On Jan 16, 4:36 pm, Tim Nelson  wrote:
>> There was a bug that's been fixed. I suggest you use the newest
>> version, which is 2.0-SNAPSHOT. 1.1 was renamed 2.0 last week.
>>
>> Tim
>>
>> On Sat, Jan 16, 2010 at 6:59 AM, Joachim A.
>>
>>
>>
>>  wrote:
>> > Hi,
>> > I've been away from Lift for quite a time. At the moment I work on an old
>> > project and am in the progress to update to the current 1.1-SNAPSHOT .
>> > I have to say that getting used to Lift again was very quick and easy.
>>
>> > In 1.0 this worked and showed a top-level menu item and submenu items if
>> > you've clicked on it:
>> >        Menu(Loc("admin_newsletter", List("newsletter"), 
>> > S.?("menu.newsletters"),
>> > testUserNotSuper), Newsletter.menus: _*) ::
>>
>> > In 1.1 the submenu items do not appear. "Newsletter" uses Crudify.
>>
>> > I've tried  the expandAll attribute for Menu.builder but this did not work.
>>
>> > I'd appreciate some hints where to look,
>>
>> > Best regards,
>> > Joachim
>>
>> > --
>> > You received this message because you are subscribed to the Google Groups 
>> > "Lift" group.
>> > To post to this group, send email to lift...@googlegroups.com.
>> > To unsubscribe from this group, send email to 
>> > liftweb+unsubscr...@googlegroups.com.
>> > For more options, visit this group 
>> > athttp://groups.google.com/group/liftweb?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Lift" group.
> To post to this group, send email to lift...@googlegroups.com.
> To unsubscribe from this group, send email to 
> liftweb+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/liftweb?hl=en.
>
>
>
>
-- 
You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to lift...@googlegroups.com.
To unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en.

[Lift] Re: 1.1: children of menu items do not appear

[Joachim A.]

Tim,
thank you for your reply.
I've updated updated to 2.0-SNAPSHOT now. The submenu items still do
not appear, though.

Do I need to set some options or is it still the bug you mentioned?

Regards,
Joachim

On Jan 16, 4:36 pm, Tim Nelson  wrote:
> There was a bug that's been fixed. I suggest you use the newest
> version, which is 2.0-SNAPSHOT. 1.1 was renamed 2.0 last week.
>
> Tim
>
> On Sat, Jan 16, 2010 at 6:59 AM, Joachim A.
>
>
>
>  wrote:
> > Hi,
> > I've been away from Lift for quite a time. At the moment I work on an old
> > project and am in the progress to update to the current 1.1-SNAPSHOT .
> > I have to say that getting used to Lift again was very quick and easy.
>
> > In 1.0 this worked and showed a top-level menu item and submenu items if
> > you've clicked on it:
> >        Menu(Loc("admin_newsletter", List("newsletter"), 
> > S.?("menu.newsletters"),
> > testUserNotSuper), Newsletter.menus: _*) ::
>
> > In 1.1 the submenu items do not appear. "Newsletter" uses Crudify.
>
> > I've tried  the expandAll attribute for Menu.builder but this did not work.
>
> > I'd appreciate some hints where to look,
>
> > Best regards,
> > Joachim
>
> > --
> > You received this message because you are subscribed to the Google Groups 
> > "Lift" group.
> > To post to this group, send email to lift...@googlegroups.com.
> > To unsubscribe from this group, send email to 
> > liftweb+unsubscr...@googlegroups.com.
> > For more options, visit this group 
> > athttp://groups.google.com/group/liftweb?hl=en.
-- 
You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to lift...@googlegroups.com.
To unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en.

[Lift] Re: 1.1-SNAPSHOT In() with OrderBy mapper bug

[David Pollak]

On Thu, Nov 5, 2009 at 3:47 PM, jon  wrote:

>
> I just verified that the newer h2 fixes the problem.  Thanks for
> investigating!
>

Sure thing.  Party on!


>
> On Nov 5, 6:33 pm, David Pollak  wrote:
> > On Wed, Nov 4, 2009 at 10:02 AM, jon  wrote:
> >
> > > Hi,
> >
> > > I just noticed OrderBy statements cause Inner selects to break in h2:
> >
> > > I query such as: User.findAll(In(User.id, Dog.owner, OrderBy(Dog.name,
> > > Ascending)), MaxRows(5))
> >
> > > Produces:
> >
> > > Message: org.h2.jdbc.JdbcSQLException: Order by expression NAME must
> > > be in the result list in this case; SQL statement:
> > > SELECT DISTINCT OWNER AS _0
> > > FROM PUBLIC.DOG /* PUBLIC.DOG_TABLE_SCAN */
> > > ORDER BY =NAME [90068-117]
> >
> > This is an issue in H2 1.1.  Please upgrade to 1.2.121 and the problem
> goes
> > away.
> >
> > If it's not possible for you to upgrade to 1.2.121, let's discuss by
> phone
> > or privately.
> >
> >
> >
> > > Code to duplicate here:
> >
> > >http://github.com/hoffrocket/lift_1_1_sample/commit/0093e2585e0d9d799.
> ..
> >
> > > This works in M5.  Any chance a workaround or fix could be put out
> > > before M7?  Sorry, I didn't notice until today.
> >
> > > Thanks,
> >
> > > Jon
> >
> > --
> > Lift, the simply functional web frameworkhttp://liftweb.net
> > Beginning Scalahttp://www.apress.com/book/view/1430219890
> > Follow me:http://twitter.com/dpp
> > Surf the harmonics
> >
>


-- 
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Surf the harmonics

--~--~-~--~~~---~--~~
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 unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: 1.1-SNAPSHOT In() with OrderBy mapper bug

[jon]

I just verified that the newer h2 fixes the problem.  Thanks for
investigating!

On Nov 5, 6:33 pm, David Pollak  wrote:
> On Wed, Nov 4, 2009 at 10:02 AM, jon  wrote:
>
> > Hi,
>
> > I just noticed OrderBy statements cause Inner selects to break in h2:
>
> > I query such as: User.findAll(In(User.id, Dog.owner, OrderBy(Dog.name,
> > Ascending)), MaxRows(5))
>
> > Produces:
>
> > Message: org.h2.jdbc.JdbcSQLException: Order by expression NAME must
> > be in the result list in this case; SQL statement:
> > SELECT DISTINCT OWNER AS _0
> > FROM PUBLIC.DOG /* PUBLIC.DOG_TABLE_SCAN */
> > ORDER BY =NAME [90068-117]
>
> This is an issue in H2 1.1.  Please upgrade to 1.2.121 and the problem goes
> away.
>
> If it's not possible for you to upgrade to 1.2.121, let's discuss by phone
> or privately.
>
>
>
> > Code to duplicate here:
>
> >http://github.com/hoffrocket/lift_1_1_sample/commit/0093e2585e0d9d799...
>
> > This works in M5.  Any chance a workaround or fix could be put out
> > before M7?  Sorry, I didn't notice until today.
>
> > Thanks,
>
> > Jon
>
> --
> Lift, the simply functional web frameworkhttp://liftweb.net
> Beginning Scalahttp://www.apress.com/book/view/1430219890
> Follow me:http://twitter.com/dpp
> Surf the harmonics
--~--~-~--~~~---~--~~
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 unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: 1.1-SNAPSHOT In() with OrderBy mapper bug

[David Pollak]

On Wed, Nov 4, 2009 at 10:02 AM, jon  wrote:

>
> Hi,
>
> I just noticed OrderBy statements cause Inner selects to break in h2:
>
> I query such as: User.findAll(In(User.id, Dog.owner, OrderBy(Dog.name,
> Ascending)), MaxRows(5))
>
> Produces:
>
> Message: org.h2.jdbc.JdbcSQLException: Order by expression NAME must
> be in the result list in this case; SQL statement:
> SELECT DISTINCT OWNER AS _0
> FROM PUBLIC.DOG /* PUBLIC.DOG_TABLE_SCAN */
> ORDER BY =NAME [90068-117]
>

This is an issue in H2 1.1.  Please upgrade to 1.2.121 and the problem goes
away.

If it's not possible for you to upgrade to 1.2.121, let's discuss by phone
or privately.


>
> Code to duplicate here:
>
>
> http://github.com/hoffrocket/lift_1_1_sample/commit/0093e2585e0d9d799b503f32da7496e212efd873
>
> This works in M5.  Any chance a workaround or fix could be put out
> before M7?  Sorry, I didn't notice until today.
>
> Thanks,
>
> Jon
> >
>


-- 
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Surf the harmonics

--~--~-~--~~~---~--~~
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 unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: 1.1-SNAPSHOT In() with OrderBy mapper bug

[David Pollak]

On Wed, Nov 4, 2009 at 11:04 AM, jon  wrote:

>
> Wow, congrats!
>

No... not that way... I've got 5 year old twins... but our nanny's on
vacation and my wife  is
way too busy on a huge case, so I'm primary childcare.


>
> On Nov 4, 1:46 pm, David Pollak  wrote:
> > On Wed, Nov 4, 2009 at 10:36 AM, jon  wrote:
> >
> > > That would be great.  Would it also be published to the scala-tools
> > > repo?
> >
> > Dunno.  Got to figure out how to get it published.  But we can work on
> that
> > tomorrow (today's release day, plus I turn into a dad @ 1pm PST)
> >
> >
> >
> >
> >
> >
> >
> > > On Nov 4, 1:18 pm, David Pollak  wrote:
> > > > On Wed, Nov 4, 2009 at 10:02 AM, jon  wrote:
> >
> > > > > Hi,
> >
> > > > > I just noticed OrderBy statements cause Inner selects to break in
> h2:
> >
> > > > > I query such as: User.findAll(In(User.id, Dog.owner,
> OrderBy(Dog.name,
> > > > > Ascending)), MaxRows(5))
> >
> > > > > Produces:
> >
> > > > > Message: org.h2.jdbc.JdbcSQLException: Order by expression NAME
> must
> > > > > be in the result list in this case; SQL statement:
> > > > > SELECT DISTINCT OWNER AS _0
> > > > > FROM PUBLIC.DOG /* PUBLIC.DOG_TABLE_SCAN */
> > > > > ORDER BY =NAME [90068-117]
> >
> > > > > Code to duplicate here:
> >
> > > > >
> http://github.com/hoffrocket/lift_1_1_sample/commit/0093e2585e0d9d799.
> > > ..
> >
> > > > > This works in M5.  Any chance a workaround or fix could be put out
> > > > > before M7?  Sorry, I didn't notice until today.
> >
> > > > How about a branch off M7 that fixes this one bug?
> >
> > > > > Thanks,
> >
> > > > > Jon
> >
> > > > --
> > > > Lift, the simply functional web frameworkhttp://liftweb.net
> > > > Beginning Scalahttp://www.apress.com/book/view/1430219890
> > > > Follow me:http://twitter.com/dpp
> > > > Surf the harmonics
> >
> > --
> > Lift, the simply functional web frameworkhttp://liftweb.net
> > Beginning Scalahttp://www.apress.com/book/view/1430219890
> > Follow me:http://twitter.com/dpp
> > Surf the harmonics
> >
>


-- 
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Surf the harmonics

--~--~-~--~~~---~--~~
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 unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: 1.1-SNAPSHOT In() with OrderBy mapper bug

[jon]

Wow, congrats!

On Nov 4, 1:46 pm, David Pollak  wrote:
> On Wed, Nov 4, 2009 at 10:36 AM, jon  wrote:
>
> > That would be great.  Would it also be published to the scala-tools
> > repo?
>
> Dunno.  Got to figure out how to get it published.  But we can work on that
> tomorrow (today's release day, plus I turn into a dad @ 1pm PST)
>
>
>
>
>
>
>
> > On Nov 4, 1:18 pm, David Pollak  wrote:
> > > On Wed, Nov 4, 2009 at 10:02 AM, jon  wrote:
>
> > > > Hi,
>
> > > > I just noticed OrderBy statements cause Inner selects to break in h2:
>
> > > > I query such as: User.findAll(In(User.id, Dog.owner, OrderBy(Dog.name,
> > > > Ascending)), MaxRows(5))
>
> > > > Produces:
>
> > > > Message: org.h2.jdbc.JdbcSQLException: Order by expression NAME must
> > > > be in the result list in this case; SQL statement:
> > > > SELECT DISTINCT OWNER AS _0
> > > > FROM PUBLIC.DOG /* PUBLIC.DOG_TABLE_SCAN */
> > > > ORDER BY =NAME [90068-117]
>
> > > > Code to duplicate here:
>
> > > >http://github.com/hoffrocket/lift_1_1_sample/commit/0093e2585e0d9d799.
> > ..
>
> > > > This works in M5.  Any chance a workaround or fix could be put out
> > > > before M7?  Sorry, I didn't notice until today.
>
> > > How about a branch off M7 that fixes this one bug?
>
> > > > Thanks,
>
> > > > Jon
>
> > > --
> > > Lift, the simply functional web frameworkhttp://liftweb.net
> > > Beginning Scalahttp://www.apress.com/book/view/1430219890
> > > Follow me:http://twitter.com/dpp
> > > Surf the harmonics
>
> --
> Lift, the simply functional web frameworkhttp://liftweb.net
> Beginning Scalahttp://www.apress.com/book/view/1430219890
> Follow me:http://twitter.com/dpp
> Surf the harmonics
--~--~-~--~~~---~--~~
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 unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: 1.1-SNAPSHOT In() with OrderBy mapper bug

[David Pollak]

On Wed, Nov 4, 2009 at 10:36 AM, jon  wrote:

>
> That would be great.  Would it also be published to the scala-tools
> repo?
>

Dunno.  Got to figure out how to get it published.  But we can work on that
tomorrow (today's release day, plus I turn into a dad @ 1pm PST)


>
> On Nov 4, 1:18 pm, David Pollak  wrote:
> > On Wed, Nov 4, 2009 at 10:02 AM, jon  wrote:
> >
> > > Hi,
> >
> > > I just noticed OrderBy statements cause Inner selects to break in h2:
> >
> > > I query such as: User.findAll(In(User.id, Dog.owner, OrderBy(Dog.name,
> > > Ascending)), MaxRows(5))
> >
> > > Produces:
> >
> > > Message: org.h2.jdbc.JdbcSQLException: Order by expression NAME must
> > > be in the result list in this case; SQL statement:
> > > SELECT DISTINCT OWNER AS _0
> > > FROM PUBLIC.DOG /* PUBLIC.DOG_TABLE_SCAN */
> > > ORDER BY =NAME [90068-117]
> >
> > > Code to duplicate here:
> >
> > >http://github.com/hoffrocket/lift_1_1_sample/commit/0093e2585e0d9d799.
> ..
> >
> > > This works in M5.  Any chance a workaround or fix could be put out
> > > before M7?  Sorry, I didn't notice until today.
> >
> > How about a branch off M7 that fixes this one bug?
> >
> >
> >
> > > Thanks,
> >
> > > Jon
> >
> > --
> > Lift, the simply functional web frameworkhttp://liftweb.net
> > Beginning Scalahttp://www.apress.com/book/view/1430219890
> > Follow me:http://twitter.com/dpp
> > Surf the harmonics
> >
>


-- 
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Surf the harmonics

--~--~-~--~~~---~--~~
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 unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: 1.1-SNAPSHOT In() with OrderBy mapper bug

[jon]

That would be great.  Would it also be published to the scala-tools
repo?

On Nov 4, 1:18 pm, David Pollak  wrote:
> On Wed, Nov 4, 2009 at 10:02 AM, jon  wrote:
>
> > Hi,
>
> > I just noticed OrderBy statements cause Inner selects to break in h2:
>
> > I query such as: User.findAll(In(User.id, Dog.owner, OrderBy(Dog.name,
> > Ascending)), MaxRows(5))
>
> > Produces:
>
> > Message: org.h2.jdbc.JdbcSQLException: Order by expression NAME must
> > be in the result list in this case; SQL statement:
> > SELECT DISTINCT OWNER AS _0
> > FROM PUBLIC.DOG /* PUBLIC.DOG_TABLE_SCAN */
> > ORDER BY =NAME [90068-117]
>
> > Code to duplicate here:
>
> >http://github.com/hoffrocket/lift_1_1_sample/commit/0093e2585e0d9d799...
>
> > This works in M5.  Any chance a workaround or fix could be put out
> > before M7?  Sorry, I didn't notice until today.
>
> How about a branch off M7 that fixes this one bug?
>
>
>
> > Thanks,
>
> > Jon
>
> --
> Lift, the simply functional web frameworkhttp://liftweb.net
> Beginning Scalahttp://www.apress.com/book/view/1430219890
> Follow me:http://twitter.com/dpp
> Surf the harmonics
--~--~-~--~~~---~--~~
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 unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: 1.1-SNAPSHOT In() with OrderBy mapper bug

[David Pollak]

On Wed, Nov 4, 2009 at 10:02 AM, jon  wrote:

>
> Hi,
>
> I just noticed OrderBy statements cause Inner selects to break in h2:
>
> I query such as: User.findAll(In(User.id, Dog.owner, OrderBy(Dog.name,
> Ascending)), MaxRows(5))
>
> Produces:
>
> Message: org.h2.jdbc.JdbcSQLException: Order by expression NAME must
> be in the result list in this case; SQL statement:
> SELECT DISTINCT OWNER AS _0
> FROM PUBLIC.DOG /* PUBLIC.DOG_TABLE_SCAN */
> ORDER BY =NAME [90068-117]
>
> Code to duplicate here:
>
>
> http://github.com/hoffrocket/lift_1_1_sample/commit/0093e2585e0d9d799b503f32da7496e212efd873
>
> This works in M5.  Any chance a workaround or fix could be put out
> before M7?  Sorry, I didn't notice until today.
>

How about a branch off M7 that fixes this one bug?


>
> Thanks,
>
> Jon
> >
>


-- 
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Surf the harmonics

--~--~-~--~~~---~--~~
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 unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: 1.1-M6 Mapped fields with dbColumnName always displaying defaultValue

[Troy Noble]

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 source tree.

I'll send you the updated
lift-persistence/lift-mapper/src/test/scala/net/liftweb/mapper/MapperSpecs.scala
file with the new tests (fails 32 tests with just Derby, H2, and H2 in
Memory... fails an additional 10 tests if I add MySQL provider that matches
your test setup), and the output I'm seeing from the surefire-reports.

Thanks again for the help, Troy

On Sat, Oct 31, 2009 at 8:56 AM, Troy Noble  wrote:

> 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 have a JDBC driver
> that requires case sensitive names... which right now is MySQL in my world.
> Most of the other RDBMSs don't have this "feature". So I don't know if I
> could contribute any automated tests that would work just within the context
> of Liftweb (or with optional embedded database) without requiring a MySQL
> server as well.  Unless we were to add a test-only attribute in the Mapper
> classes that turns on quoting of column & field name and uses an embedded H2
> in-memory database.  Yuck!
>
> I would be willing to contribute some UNIT tests if I can figure out where
> to do it.  Is there some extractor/observer style mechanism in the Mapper
> classes that would allow me to intercept the SQL statements that can be run
> in the absence of the DBMS driver?
>
> Thanks again, Troy
>
>
> On Sat, Oct 31, 2009 at 8:09 AM, David Pollak <
> feeder.of.the.be...@gmail.com> wrote:
>
>> 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  wrote:
>>
>>> 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 sensitive on naming).
>>>
>>> David, I sent you an offline e-mail with all the details.  I can open
>>> another ticket if you want.  I am willing to keep testing with MySQL if you
>>> want as we work through these issues.
>>>
>>> I wish H2 or one of the other embedded databases supported case sensitive
>>> table & column names so I could give you a tidy offline test case.  H2 does
>>> not appear to support case sensitive names unless you surround them with
>>> double quotes such as "TABLE_NAME".
>>>
>>> I know I'm not supposed to use MySQL per earlier postings on this list,
>>> but I have about 15 databases already existing in MySQL and we wanted to
>>> start using Lift with some of them.  It'll take me quite some time to
>>> re-target Postgres or other DBMS.
>>>
>>> Thanks again for all your help, Troy
>>>
>>>
>>> On Fri, Oct 30, 2009 at 4:13 PM, David Pollak <
>>> feeder.of.the.be...@gmail.com> wrote:
>>>


 On Fri, Oct 30, 2009 at 3:06 PM, Troy Noble 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 latest has built.

 Then do: mvn -U clean install jetty:run

 The "-U" forces Maven to check the repositories for the latest.


>
> 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.  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 
>>
>>
>>> I have seen EXACTLY same behavior when dbColumnName returned
>>> _upcased_ names
>>>
>>> lopex
>>>
>>>
>>>
>>
>>
>> --
>> Lift, the simply functional web framework http://liftweb.net
>> Beginning Scala http://www.apress.com/book/view/1430219890
>> Follow me: http://twitter.com/dpp
>> Surf the harmonics
>>
>>
>>
>
>
>


 --
 Lift, the simply functional web framework http://liftweb.net
 Beginning Scala http://www.apress.com/book/view/1430219890
 Follow me: http://twitter.com/dpp

[Lift] Re: 1.1-M6 Mapped fields with dbColumnName always displaying defaultValue

[Troy Noble]

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 have a JDBC driver
that requires case sensitive names... which right now is MySQL in my world.
Most of the other RDBMSs don't have this "feature". So I don't know if I
could contribute any automated tests that would work just within the context
of Liftweb (or with optional embedded database) without requiring a MySQL
server as well.  Unless we were to add a test-only attribute in the Mapper
classes that turns on quoting of column & field name and uses an embedded H2
in-memory database.  Yuck!

I would be willing to contribute some UNIT tests if I can figure out where
to do it.  Is there some extractor/observer style mechanism in the Mapper
classes that would allow me to intercept the SQL statements that can be run
in the absence of the DBMS driver?

Thanks again, Troy

On Sat, Oct 31, 2009 at 8:09 AM, David Pollak  wrote:

> 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  wrote:
>
>> 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
>> sensitive on naming).
>>
>> David, I sent you an offline e-mail with all the details.  I can open
>> another ticket if you want.  I am willing to keep testing with MySQL if you
>> want as we work through these issues.
>>
>> I wish H2 or one of the other embedded databases supported case sensitive
>> table & column names so I could give you a tidy offline test case.  H2 does
>> not appear to support case sensitive names unless you surround them with
>> double quotes such as "TABLE_NAME".
>>
>> I know I'm not supposed to use MySQL per earlier postings on this list,
>> but I have about 15 databases already existing in MySQL and we wanted to
>> start using Lift with some of them.  It'll take me quite some time to
>> re-target Postgres or other DBMS.
>>
>> Thanks again for all your help, Troy
>>
>>
>> On Fri, Oct 30, 2009 at 4:13 PM, David Pollak <
>> feeder.of.the.be...@gmail.com> wrote:
>>
>>>
>>>
>>> On Fri, Oct 30, 2009 at 3:06 PM, Troy Noble  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 latest has built.
>>>
>>> Then do: mvn -U clean install jetty:run
>>>
>>> The "-U" forces Maven to check the repositories for the latest.
>>>
>>>

 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.  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 
>
>
>> I have seen EXACTLY same behavior when dbColumnName returned _upcased_
>> names
>>
>> lopex
>>
>>
>>
>
>
> --
> Lift, the simply functional web framework http://liftweb.net
> Beginning Scala http://www.apress.com/book/view/1430219890
> Follow me: http://twitter.com/dpp
> Surf the harmonics
>
>
>



>>>
>>>
>>> --
>>> Lift, the simply functional web framework http://liftweb.net
>>> Beginning Scala http://www.apress.com/book/view/1430219890
>>> Follow me: http://twitter.com/dpp
>>> Surf the harmonics
>>>
>>>
>>>
>>
>>
>>
>
>
> --
> Lift, the simply functional web framework http://liftweb.net
> Beginning Scala http://www.apress.com/book/view/1430219890
> Follow me: http://twitter.com/dpp
> Surf the harmonics
>
> >
>

--~--~-~--~~~---~--~~
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 unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: 1.1-M6 Mapped fields with dbColumnName always displaying defaultValue

[David Pollak]

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  wrote:

> 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
> sensitive on naming).
>
> David, I sent you an offline e-mail with all the details.  I can open
> another ticket if you want.  I am willing to keep testing with MySQL if you
> want as we work through these issues.
>
> I wish H2 or one of the other embedded databases supported case sensitive
> table & column names so I could give you a tidy offline test case.  H2 does
> not appear to support case sensitive names unless you surround them with
> double quotes such as "TABLE_NAME".
>
> I know I'm not supposed to use MySQL per earlier postings on this list, but
> I have about 15 databases already existing in MySQL and we wanted to start
> using Lift with some of them.  It'll take me quite some time to re-target
> Postgres or other DBMS.
>
> Thanks again for all your help, Troy
>
>
> On Fri, Oct 30, 2009 at 4:13 PM, David Pollak <
> feeder.of.the.be...@gmail.com> wrote:
>
>>
>>
>> On Fri, Oct 30, 2009 at 3:06 PM, Troy Noble  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 latest has built.
>>
>> Then do: mvn -U clean install jetty:run
>>
>> The "-U" forces Maven to check the repositories for the latest.
>>
>>
>>>
>>> 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.  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 


> I have seen EXACTLY same behavior when dbColumnName returned _upcased_
> names
>
> lopex
>
>
>


 --
 Lift, the simply functional web framework http://liftweb.net
 Beginning Scala http://www.apress.com/book/view/1430219890
 Follow me: http://twitter.com/dpp
 Surf the harmonics



>>>
>>>
>>>
>>
>>
>> --
>> Lift, the simply functional web framework http://liftweb.net
>> Beginning Scala http://www.apress.com/book/view/1430219890
>> Follow me: http://twitter.com/dpp
>> Surf the harmonics
>>
>>
>>
>
> >
>


-- 
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Surf the harmonics

--~--~-~--~~~---~--~~
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 unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: 1.1-M6 Mapped fields with dbColumnName always displaying defaultValue

[Troy Noble]

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
sensitive on naming).

David, I sent you an offline e-mail with all the details.  I can open
another ticket if you want.  I am willing to keep testing with MySQL if you
want as we work through these issues.

I wish H2 or one of the other embedded databases supported case sensitive
table & column names so I could give you a tidy offline test case.  H2 does
not appear to support case sensitive names unless you surround them with
double quotes such as "TABLE_NAME".

I know I'm not supposed to use MySQL per earlier postings on this list, but
I have about 15 databases already existing in MySQL and we wanted to start
using Lift with some of them.  It'll take me quite some time to re-target
Postgres or other DBMS.

Thanks again for all your help, Troy

On Fri, Oct 30, 2009 at 4:13 PM, David Pollak  wrote:

>
>
> On Fri, Oct 30, 2009 at 3:06 PM, Troy Noble  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 latest has built.
>
> Then do: mvn -U clean install jetty:run
>
> The "-U" forces Maven to check the repositories for the latest.
>
>
>>
>> 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.  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 
>>>
>>>
 I have seen EXACTLY same behavior when dbColumnName returned _upcased_
 names

 lopex



>>>
>>>
>>> --
>>> Lift, the simply functional web framework http://liftweb.net
>>> Beginning Scala http://www.apress.com/book/view/1430219890
>>> Follow me: http://twitter.com/dpp
>>> Surf the harmonics
>>>
>>>
>>>
>>
>>
>>
>
>
> --
> Lift, the simply functional web framework http://liftweb.net
> Beginning Scala http://www.apress.com/book/view/1430219890
> Follow me: http://twitter.com/dpp
> Surf the harmonics
>
> >
>

--~--~-~--~~~---~--~~
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 unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: 1.1-M6 Mapped fields with dbColumnName always displaying defaultValue

[David Pollak]

On Fri, Oct 30, 2009 at 3:06 PM, Troy Noble  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 latest has built.

Then do: mvn -U clean install jetty:run

The "-U" forces Maven to check the repositories for the latest.


>
> 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.  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 
>>
>>
>>> I have seen EXACTLY same behavior when dbColumnName returned _upcased_
>>> names
>>>
>>> lopex
>>>
>>>
>>>
>>
>>
>> --
>> Lift, the simply functional web framework http://liftweb.net
>> Beginning Scala http://www.apress.com/book/view/1430219890
>> Follow me: http://twitter.com/dpp
>> Surf the harmonics
>>
>>
>>
>
> >
>


-- 
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Surf the harmonics

--~--~-~--~~~---~--~~
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 unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: 1.1-M6 Mapped fields with dbColumnName always displaying defaultValue

[Troy Noble]

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  wrote:

> 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 
>
>
>> I have seen EXACTLY same behavior when dbColumnName returned _upcased_
>> names
>>
>> lopex
>>
>>
>>
>
>
> --
> Lift, the simply functional web framework http://liftweb.net
> Beginning Scala http://www.apress.com/book/view/1430219890
> Follow me: http://twitter.com/dpp
> Surf the harmonics
>
> >
>

--~--~-~--~~~---~--~~
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 unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: 1.1-M6 Mapped fields with dbColumnName always displaying defaultValue

[David Pollak]

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 

>
> I have seen EXACTLY same behavior when dbColumnName returned _upcased_
> names
>
> lopex
>
> >
>


-- 
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Surf the harmonics

--~--~-~--~~~---~--~~
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 unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: 1.1-M6 Mapped fields with dbColumnName always displaying defaultValue

[Marcin Mielżyński]

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 unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: 1.1-M6 Mapped fields with dbColumnName always displaying defaultValue

[Troy Noble]

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 behavior as well as
two other odd behaviors related to dbColumnName:
==> schemify tries to ALTER TABLE to add the columns that override
dbColumnName a second time, and of course fails with duplicate column name
exception.
==> CRUDify gets confused when I use a '  def primaryKeyField =
projectTypeId' and when projectTypeId uses 'override def dbColumnName =
'PROJECT_TYPE_ID" (see complete DDL below) where it creates all the links in
the "List" page with '-1' for the ID such as /PROJECT_TYPE/view/-1 or
/PROJECT_TYPE/edit/-1 instead of the proper PROJECT_TYPE_ID such as
.../view/1 or .../edit/1.  I think it's because these are all coming back as
-1 from the Mapper.

Here's schemify's DDL output and stack trace... just for grins... my ticket
will include this as well of course.

INFO - CREATE TABLE todo (priority INTEGER , id BIGINT NOT NULL
AUTO_INCREMENT ,
 desc_c VARCHAR(128) , done BOOLEAN , owner BIGINT)
INFO - ALTER TABLE todo ADD CONSTRAINT todo_PK PRIMARY KEY(id)
INFO - CREATE TABLE PROJECT_TYPE (ACTIVE BOOLEAN , val4 VARCHAR(128) , val3
VARC
HAR(128) , val2 INTEGER , val1 BIGINT , LAST_MODIFIED_BY VARCHAR(30) ,
GUI_PROJE
CT_LIST_VISIBLE BOOLEAN , GUI_TREE_VISIBLE BOOLEAN , GUI_NAME VARCHAR(25) ,
type
_name VARCHAR(25) , create_date TIMESTAMP , PROJECT_TYPE_ID BIGINT NOT NULL
AUTO
_INCREMENT)
INFO - ALTER TABLE PROJECT_TYPE ADD CONSTRAINT PROJECT_TYPE_PK PRIMARY
KEY(PROJE
CT_TYPE_ID)
INFO - ALTER TABLE PROJECT_TYPE ADD COLUMN ACTIVE BOOLEAN
ERROR - Failed to Boot
org.h2.jdbc.JdbcSQLException: Duplicate column name ACTIVE; SQL statement:

---> ALTER TABLE PROJECT_TYPE ADD COLUMN ACTIVE BOOLEAN [42121-121]

at org.h2.message.Message.getSQLException(Message.java:106)
at org.h2.message.Message.getSQLException(Message.java:117)
at org.h2.message.Message.getSQLException(Message.java:76)
at org.h2.table.Table.setColumns(Table.java:336)
at org.h2.table.TableData.(TableData.java:82)
at org.h2.schema.Schema.createTable(Schema.java:492)
at
org.h2.command.ddl.AlterTableAlterColumn.copyData(AlterTableAlterColu
mn.java:256)
at
org.h2.command.ddl.AlterTableAlterColumn.update(AlterTableAlterColumn
.java:162)
at org.h2.command.CommandContainer.update(CommandContainer.java:72)
at org.h2.command.Command.executeUpdate(Command.java:208)
at org.h2.jdbc.JdbcStatement.execute(JdbcStatement.java:162)
at
net.liftweb.mapper.Schemifier$.net$liftweb$mapper$Schemifier$$maybeWr
ite(Schemifier.scala:151)
at
net.liftweb.mapper.Schemifier$$anonfun$6$$anonfun$apply$10.apply(Sche
mifier.scala:207)
at
net.liftweb.mapper.Schemifier$$anonfun$6$$anonfun$apply$10.apply(Sche
mifier.scala:206)
at scala.List.foreach(List.scala:841)
at
net.liftweb.mapper.Schemifier$$anonfun$6.apply(Schemifier.scala:205)
at
net.liftweb.mapper.Schemifier$$anonfun$6.apply(Schemifier.scala:187)
at scala.List.flatMap(List.scala:1132)
at
net.liftweb.mapper.Schemifier$.net$liftweb$mapper$Schemifier$$ensureC
olumns(Schemifier.scala:186)
at
net.liftweb.mapper.Schemifier$$anonfun$schemify$1$$anonfun$2.apply(Sc
hemifier.scala:62)
at
net.liftweb.mapper.Schemifier$$anonfun$schemify$1$$anonfun$2.apply(Sc
hemifier.scala:62)
at scala.List.foldLeft(List.scala:1066)
at
net.liftweb.mapper.Schemifier$$anonfun$schemify$1.apply(Schemifier.sc
ala:62)
at
net.liftweb.mapper.Schemifier$$anonfun$schemify$1.apply(Schemifier.sc
ala:55)
at net.liftweb.mapper.DB$.use(DB.scala:419)
at net.liftweb.mapper.Schemifier$.schemify(Schemifier.scala:54)
at net.liftweb.mapper.Schemifier$.schemify(Schemifier.scala:37)
at bootstrap.liftweb.Boot.boot(Boot.scala:29)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
net.liftweb.util.ClassHelpers$$anonfun$createInvoker$1.apply(ClassHel
pers.scala:409)
at
net.liftweb.util.ClassHelpers$$anonfun$createInvoker$1.apply(ClassHel
pers.scala:407)
at
net.liftweb.http.DefaultBootstrap$$anonfun$boot$1.apply(LiftRules.sca
la:1188)
at
net.liftweb.http.DefaultBootstrap$$anonfun$boot$1.apply(LiftRules.sca
la:1188)
at net.liftweb.common.Full.map(Box.scala:330)
at net.liftweb.http.DefaultBootstrap$.boot(LiftRules.scala:1188)
at
net.liftweb.http.provider.HTTPProvider$class.bootLift(HTTPProvider.sc
ala:70)
at net.liftweb.http.LiftFilter.boo

[Lift] Re: 1.1-M6 Mapped fields with dbColumnName always displaying defaultValue

[David Pollak]

On Thu, Oct 29, 2009 at 10:15 PM, Troy Noble  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:
>
>  object createDate extends MappedDateTime(this) {
>override def dbColumnName = "CREATE_DATE"
>  }
>
> When we added "with CRUDify" the resulting List and Edit forms all
> display this fields as Jan 01, 1970 all the time.  We tried this
> experiment also with other columns of different types (MappedString,
> MappedInt, MappedFriendlyString, MappedDouble, MappedBoolean) and
> these all seemed to always display the default value rather than the
> real data value from the database column.
>

This should have nothing to do with CRUDify.

Can you provide a simple DDL and a very simple Lift app (along with the DB
version you're running against) and we'll look into (please open a ticket)?


>
> We weren't sure if it was CRUDify or Mapper causing the problem.  I
> think we narrowed it down to the Mapper by creating our own simple
> snippet to create a basic HTML table and bound this value using
>
> class ProjType {
>  def projects(xhtml: NodeSeq): NodeSeq =
> ProjectType.findAll(OrderBy(ProjectType.createDate, Ascending))
>  .flatMap(aProjType => bind("projtype", xhtml,
> "createDate" -> aProjType.createDate))
> }
>
> and our xhtml section that uses this snippet is:
>
>  
>   
>
>  01/01/2009
>
>   
>  
>
> but createDate is still coming back Jan 01, 1970 in our custom
> rendered table.
>
> If we instead changed our mapped field name in our class to match the
> legacy column name (CREATE_DATE) exactly:
>
>  object CREATE_DATE extends MappedDateTime(this)
>
> and our binding to "createDate" -> aProjType.CREATE_DATE
>
> everything is happy (both CRUDify and our custom form).
>
> We're not sure if this is a bug or if we're doing something wrong.
>
> Thanks, Troy
>
> >
>


-- 
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Surf the harmonics

--~--~-~--~~~---~--~~
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 unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: 1.1

[Timothy Perrett]

Your welcome Jack. Have fun.

Cheers, Tim

On 25 Oct 2009, at 18:28, Jack Widman wrote:

> Thanks Tim. And next time I will search more before asking.


--~--~-~--~~~---~--~~
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 unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: 1.1

[Jack Widman]

Thanks Tim. And next time I will search more before asking.

On Sun, Oct 25, 2009 at 2:26 PM, Timothy Perrett wrote:

>
> Jack,
>
> This question has been asked quite a number of times recently on list.
>
> Change:
>
> 1.0
>
> on the liftweb dependencies in your pom.xml to be:
>
> 1.1-SNAPSHOT
>
> That will give you the latest HEAD build. If you want a known point in
> time, use M6:
>
> 1.1-M6
>
> Cheers, Tim
>
> On Oct 25, 6:00 pm, jack  wrote:
> > I have been using lift 1.0. What is the best way to upgrade to 1.1?
> >
>


-- 
Jack Widman

co-founder / cto,  Authoritude, Inc.

203-641-9355

--~--~-~--~~~---~--~~
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 unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: 1.1

[Timothy Perrett]

Jack,

This question has been asked quite a number of times recently on list.

Change:

1.0

on the liftweb dependencies in your pom.xml to be:

1.1-SNAPSHOT

That will give you the latest HEAD build. If you want a known point in
time, use M6:

1.1-M6

Cheers, Tim

On Oct 25, 6:00 pm, jack  wrote:
> I have been using lift 1.0. What is the best way to upgrade to 1.1?
--~--~-~--~~~---~--~~
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 unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: 1.1-SNAPSHOT and Snippet problems?

[Thomas Rampelberg]

Anyways, I was definitely screwed up ... forcing maven to actually do
what it was supposed to fixed my problem. Thanks for the pointer
Marius.

~Thomas

On Sat, Oct 3, 2009 at 5:39 PM, Thomas Rampelberg  wrote:
> I thought that I'd just updated all the versions . from that stack
> trace, how do you tell which version lift-util is?
>
> On Sat, Oct 3, 2009 at 1:39 PM, marius d.  wrote:
>>
>> What verions of lift are you using? It appears that lift-util is a
>> different version than lift ?
>>
>> Br's,
>> Marius
>>
>> On Oct 3, 11:11 pm, Thomas Rampelberg  wrote:
>>> I just synced up to main this morning and now whenever I try and use
>>> one of my snippets, I'm getting the traceback below. Any hints on what
>>> I'm doing wrong? The snippet in question is just the basic
>>> Util.in/Util.out that the tutorial has you write.
>>>
>>>       
>>>         
>>>           
>>>         
>>>         
>>>           
>>>             You must be logged in to view this content.
>>>             Login
>>>           
>>>         
>>>       
>>>
>>> class Util {
>>>   def in(html: NodeSeq) =
>>>     if (User.loggedIn_?) html else NodeSeq.Empty
>>>
>>>   def out(html: NodeSeq) =
>>>     if (!User.loggedIn_?) html else NodeSeq.Empty
>>>
>>> }
>>>
>>> Message: java.lang.AbstractMethodError:
>>> net.liftweb.util.Helpers$.tryo(Lscala/PartialFunction;Lscala/Function0;)Lnet/liftweb/util/Box;
>>>         
>>> net.liftweb.http.LiftSession.net$liftweb$http$LiftSession$$instantiateOrRedirect(LiftSession.scala:862)
>>>         
>>> net.liftweb.http.LiftSession$$anonfun$net$liftweb$http$LiftSession$$findSnippetInstance$1$$anonfun$apply$41.apply(LiftSession.scala:911)
>>>         
>>> net.liftweb.http.LiftSession$$anonfun$net$liftweb$http$LiftSession$$findSnippetInstance$1$$anonfun$apply$41.apply(LiftSession.scala:911)
>>>         net.liftweb.util.Full.flatMap(Box.scala:332)
>>>         
>>> net.liftweb.http.LiftSession$$anonfun$net$liftweb$http$LiftSession$$findSnippetInstance$1.apply(LiftSession.scala:911)
>>>         
>>> net.liftweb.http.LiftSession$$anonfun$net$liftweb$http$LiftSession$$findSnippetInstance$1.apply(LiftSession.scala:911)
>>>         net.liftweb.util.EmptyBox.or(Box.scala:374)
>>>         
>>> net.liftweb.http.LiftSession.net$liftweb$http$LiftSession$$findSnippetInstance(LiftSession.scala:910)
>>>         
>>> net.liftweb.http.LiftSession$$anonfun$locateAndCacheSnippet$1$1$$anonfun$17.apply(LiftSession.scala:967)
>>>         
>>> net.liftweb.http.LiftSession$$anonfun$locateAndCacheSnippet$1$1$$anonfun$17.apply(LiftSession.scala:967)
>>>         net.liftweb.util.EmptyBox.or(Box.scala:374)
>>>         
>>> net.liftweb.http.LiftSession$$anonfun$locateAndCacheSnippet$1$1.apply(LiftSession.scala:967)
>>>         
>>> net.liftweb.http.LiftSession$$anonfun$locateAndCacheSnippet$1$1.apply(LiftSession.scala:966)
>>>         net.liftweb.util.EmptyBox.or(Box.scala:374)
>>>         
>>> net.liftweb.http.LiftSession.locateAndCacheSnippet$1(LiftSession.scala:966)
>>>         
>>> net.liftweb.http.LiftSession$$anonfun$18$$anonfun$apply$45$$anonfun$apply$48$$anonfun$apply$50.apply(LiftSession.scala:978)
>>>         
>>> net.liftweb.http.LiftSession$$anonfun$18$$anonfun$apply$45$$anonfun$apply$48$$anonfun$apply$50.apply(LiftSession.scala:976)
>>>         net.liftweb.util.EmptyBox.openOr(Box.scala:372)
>>>         
>>> net.liftweb.http.LiftSession$$anonfun$18$$anonfun$apply$45$$anonfun$apply$48.apply(LiftSession.scala:976)
>>>         
>>> net.liftweb.http.LiftSession$$anonfun$18$$anonfun$apply$45$$anonfun$apply$48.apply(LiftSession.scala:976)
>>>         net.liftweb.util.EmptyBox.openOr(Box.scala:372)
>>>         
>>> net.liftweb.http.LiftSession$$anonfun$18$$anonfun$apply$45.apply(LiftSession.scala:975)
>>>         
>>> net.liftweb.http.LiftSession$$anonfun$18$$anonfun$apply$45.apply(LiftSession.scala:975)
>>>         net.liftweb.http.S$.doSnippet(S.scala:1586)
>>>         
>>> net.liftweb.http.LiftSession$$anonfun$18.apply(LiftSession.scala:973)
>>>         
>>> net.liftweb.http.LiftSession$$anonfun$18.apply(LiftSession.scala:972)
>>>         net.liftweb.util.Full.map(Box.scala:330)
>>>         
>>> net.liftweb.http.LiftSession.net$liftweb$http$LiftSession$$processSnippet(LiftSession.scala:972)
>>>         
>>> net.liftweb.http.LiftSession$$anonfun$_defaultLiftTagProcessing$1.apply(LiftSession.scala:1073)
>>>         
>>> net.liftweb.http.LiftSession$$anonfun$_defaultLiftTagProcessing$1.apply(LiftSession.scala:1061)
>>>         net.liftweb.util.NamedPF.apply(NamedPartialFunction.scala:30)
>>>         net.liftweb.util.NamedPF$.apply(NamedPartialFunction.scala:76)
>>>         
>>> net.liftweb.http.LiftSession$$anonfun$processSurroundAndInclude$1$$anonfun$apply$57$$anonfun$apply$58$$anonfun$apply$59.apply(LiftSession.scala:1094)
>>>         
>>> net.liftweb.http.LiftSession$$anonfun$processSurroundAndInclude$1$$anonfun$apply$57$$anonfun$apply$58$$anonfun$apply$59.apply(LiftSession.scala:1094)
>>>         net.liftweb.util.ThreadGlobal

[Lift] Re: 1.1-SNAPSHOT and Snippet problems?

[Thomas Rampelberg]

I thought that I'd just updated all the versions . from that stack
trace, how do you tell which version lift-util is?

On Sat, Oct 3, 2009 at 1:39 PM, marius d.  wrote:
>
> What verions of lift are you using? It appears that lift-util is a
> different version than lift ?
>
> Br's,
> Marius
>
> On Oct 3, 11:11 pm, Thomas Rampelberg  wrote:
>> I just synced up to main this morning and now whenever I try and use
>> one of my snippets, I'm getting the traceback below. Any hints on what
>> I'm doing wrong? The snippet in question is just the basic
>> Util.in/Util.out that the tutorial has you write.
>>
>>       
>>         
>>           
>>         
>>         
>>           
>>             You must be logged in to view this content.
>>             Login
>>           
>>         
>>       
>>
>> class Util {
>>   def in(html: NodeSeq) =
>>     if (User.loggedIn_?) html else NodeSeq.Empty
>>
>>   def out(html: NodeSeq) =
>>     if (!User.loggedIn_?) html else NodeSeq.Empty
>>
>> }
>>
>> Message: java.lang.AbstractMethodError:
>> net.liftweb.util.Helpers$.tryo(Lscala/PartialFunction;Lscala/Function0;)Lnet/liftweb/util/Box;
>>         
>> net.liftweb.http.LiftSession.net$liftweb$http$LiftSession$$instantiateOrRedirect(LiftSession.scala:862)
>>         
>> net.liftweb.http.LiftSession$$anonfun$net$liftweb$http$LiftSession$$findSnippetInstance$1$$anonfun$apply$41.apply(LiftSession.scala:911)
>>         
>> net.liftweb.http.LiftSession$$anonfun$net$liftweb$http$LiftSession$$findSnippetInstance$1$$anonfun$apply$41.apply(LiftSession.scala:911)
>>         net.liftweb.util.Full.flatMap(Box.scala:332)
>>         
>> net.liftweb.http.LiftSession$$anonfun$net$liftweb$http$LiftSession$$findSnippetInstance$1.apply(LiftSession.scala:911)
>>         
>> net.liftweb.http.LiftSession$$anonfun$net$liftweb$http$LiftSession$$findSnippetInstance$1.apply(LiftSession.scala:911)
>>         net.liftweb.util.EmptyBox.or(Box.scala:374)
>>         
>> net.liftweb.http.LiftSession.net$liftweb$http$LiftSession$$findSnippetInstance(LiftSession.scala:910)
>>         
>> net.liftweb.http.LiftSession$$anonfun$locateAndCacheSnippet$1$1$$anonfun$17.apply(LiftSession.scala:967)
>>         
>> net.liftweb.http.LiftSession$$anonfun$locateAndCacheSnippet$1$1$$anonfun$17.apply(LiftSession.scala:967)
>>         net.liftweb.util.EmptyBox.or(Box.scala:374)
>>         
>> net.liftweb.http.LiftSession$$anonfun$locateAndCacheSnippet$1$1.apply(LiftSession.scala:967)
>>         
>> net.liftweb.http.LiftSession$$anonfun$locateAndCacheSnippet$1$1.apply(LiftSession.scala:966)
>>         net.liftweb.util.EmptyBox.or(Box.scala:374)
>>         
>> net.liftweb.http.LiftSession.locateAndCacheSnippet$1(LiftSession.scala:966)
>>         
>> net.liftweb.http.LiftSession$$anonfun$18$$anonfun$apply$45$$anonfun$apply$48$$anonfun$apply$50.apply(LiftSession.scala:978)
>>         
>> net.liftweb.http.LiftSession$$anonfun$18$$anonfun$apply$45$$anonfun$apply$48$$anonfun$apply$50.apply(LiftSession.scala:976)
>>         net.liftweb.util.EmptyBox.openOr(Box.scala:372)
>>         
>> net.liftweb.http.LiftSession$$anonfun$18$$anonfun$apply$45$$anonfun$apply$48.apply(LiftSession.scala:976)
>>         
>> net.liftweb.http.LiftSession$$anonfun$18$$anonfun$apply$45$$anonfun$apply$48.apply(LiftSession.scala:976)
>>         net.liftweb.util.EmptyBox.openOr(Box.scala:372)
>>         
>> net.liftweb.http.LiftSession$$anonfun$18$$anonfun$apply$45.apply(LiftSession.scala:975)
>>         
>> net.liftweb.http.LiftSession$$anonfun$18$$anonfun$apply$45.apply(LiftSession.scala:975)
>>         net.liftweb.http.S$.doSnippet(S.scala:1586)
>>         net.liftweb.http.LiftSession$$anonfun$18.apply(LiftSession.scala:973)
>>         net.liftweb.http.LiftSession$$anonfun$18.apply(LiftSession.scala:972)
>>         net.liftweb.util.Full.map(Box.scala:330)
>>         
>> net.liftweb.http.LiftSession.net$liftweb$http$LiftSession$$processSnippet(LiftSession.scala:972)
>>         
>> net.liftweb.http.LiftSession$$anonfun$_defaultLiftTagProcessing$1.apply(LiftSession.scala:1073)
>>         
>> net.liftweb.http.LiftSession$$anonfun$_defaultLiftTagProcessing$1.apply(LiftSession.scala:1061)
>>         net.liftweb.util.NamedPF.apply(NamedPartialFunction.scala:30)
>>         net.liftweb.util.NamedPF$.apply(NamedPartialFunction.scala:76)
>>         
>> net.liftweb.http.LiftSession$$anonfun$processSurroundAndInclude$1$$anonfun$apply$57$$anonfun$apply$58$$anonfun$apply$59.apply(LiftSession.scala:1094)
>>         
>> net.liftweb.http.LiftSession$$anonfun$processSurroundAndInclude$1$$anonfun$apply$57$$anonfun$apply$58$$anonfun$apply$59.apply(LiftSession.scala:1094)
>>         net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
>>         net.liftweb.http.S$.setVars(S.scala:1414)
>>         
>> net.liftweb.http.LiftSession$$anonfun$processSurroundAndInclude$1$$anonfun$apply$57$$anonfun$apply$58.apply(LiftSession.scala:1093)
>>         
>> net.liftweb.http.LiftSession$$anonfun$processSurroundAndInclude$1$$anonfun$

[Lift] Re: 1.1-SNAPSHOT and Snippet problems?

[marius d.]

What verions of lift are you using? It appears that lift-util is a
different version than lift ?

Br's,
Marius

On Oct 3, 11:11 pm, Thomas Rampelberg  wrote:
> I just synced up to main this morning and now whenever I try and use
> one of my snippets, I'm getting the traceback below. Any hints on what
> I'm doing wrong? The snippet in question is just the basic
> Util.in/Util.out that the tutorial has you write.
>
>       
>         
>           
>         
>         
>           
>             You must be logged in to view this content.
>             Login
>           
>         
>       
>
> class Util {
>   def in(html: NodeSeq) =
>     if (User.loggedIn_?) html else NodeSeq.Empty
>
>   def out(html: NodeSeq) =
>     if (!User.loggedIn_?) html else NodeSeq.Empty
>
> }
>
> Message: java.lang.AbstractMethodError:
> net.liftweb.util.Helpers$.tryo(Lscala/PartialFunction;Lscala/Function0;)Lnet/liftweb/util/Box;
>         
> net.liftweb.http.LiftSession.net$liftweb$http$LiftSession$$instantiateOrRedirect(LiftSession.scala:862)
>         
> net.liftweb.http.LiftSession$$anonfun$net$liftweb$http$LiftSession$$findSnippetInstance$1$$anonfun$apply$41.apply(LiftSession.scala:911)
>         
> net.liftweb.http.LiftSession$$anonfun$net$liftweb$http$LiftSession$$findSnippetInstance$1$$anonfun$apply$41.apply(LiftSession.scala:911)
>         net.liftweb.util.Full.flatMap(Box.scala:332)
>         
> net.liftweb.http.LiftSession$$anonfun$net$liftweb$http$LiftSession$$findSnippetInstance$1.apply(LiftSession.scala:911)
>         
> net.liftweb.http.LiftSession$$anonfun$net$liftweb$http$LiftSession$$findSnippetInstance$1.apply(LiftSession.scala:911)
>         net.liftweb.util.EmptyBox.or(Box.scala:374)
>         
> net.liftweb.http.LiftSession.net$liftweb$http$LiftSession$$findSnippetInstance(LiftSession.scala:910)
>         
> net.liftweb.http.LiftSession$$anonfun$locateAndCacheSnippet$1$1$$anonfun$17.apply(LiftSession.scala:967)
>         
> net.liftweb.http.LiftSession$$anonfun$locateAndCacheSnippet$1$1$$anonfun$17.apply(LiftSession.scala:967)
>         net.liftweb.util.EmptyBox.or(Box.scala:374)
>         
> net.liftweb.http.LiftSession$$anonfun$locateAndCacheSnippet$1$1.apply(LiftSession.scala:967)
>         
> net.liftweb.http.LiftSession$$anonfun$locateAndCacheSnippet$1$1.apply(LiftSession.scala:966)
>         net.liftweb.util.EmptyBox.or(Box.scala:374)
>         
> net.liftweb.http.LiftSession.locateAndCacheSnippet$1(LiftSession.scala:966)
>         
> net.liftweb.http.LiftSession$$anonfun$18$$anonfun$apply$45$$anonfun$apply$48$$anonfun$apply$50.apply(LiftSession.scala:978)
>         
> net.liftweb.http.LiftSession$$anonfun$18$$anonfun$apply$45$$anonfun$apply$48$$anonfun$apply$50.apply(LiftSession.scala:976)
>         net.liftweb.util.EmptyBox.openOr(Box.scala:372)
>         
> net.liftweb.http.LiftSession$$anonfun$18$$anonfun$apply$45$$anonfun$apply$48.apply(LiftSession.scala:976)
>         
> net.liftweb.http.LiftSession$$anonfun$18$$anonfun$apply$45$$anonfun$apply$48.apply(LiftSession.scala:976)
>         net.liftweb.util.EmptyBox.openOr(Box.scala:372)
>         
> net.liftweb.http.LiftSession$$anonfun$18$$anonfun$apply$45.apply(LiftSession.scala:975)
>         
> net.liftweb.http.LiftSession$$anonfun$18$$anonfun$apply$45.apply(LiftSession.scala:975)
>         net.liftweb.http.S$.doSnippet(S.scala:1586)
>         net.liftweb.http.LiftSession$$anonfun$18.apply(LiftSession.scala:973)
>         net.liftweb.http.LiftSession$$anonfun$18.apply(LiftSession.scala:972)
>         net.liftweb.util.Full.map(Box.scala:330)
>         
> net.liftweb.http.LiftSession.net$liftweb$http$LiftSession$$processSnippet(LiftSession.scala:972)
>         
> net.liftweb.http.LiftSession$$anonfun$_defaultLiftTagProcessing$1.apply(LiftSession.scala:1073)
>         
> net.liftweb.http.LiftSession$$anonfun$_defaultLiftTagProcessing$1.apply(LiftSession.scala:1061)
>         net.liftweb.util.NamedPF.apply(NamedPartialFunction.scala:30)
>         net.liftweb.util.NamedPF$.apply(NamedPartialFunction.scala:76)
>         
> net.liftweb.http.LiftSession$$anonfun$processSurroundAndInclude$1$$anonfun$apply$57$$anonfun$apply$58$$anonfun$apply$59.apply(LiftSession.scala:1094)
>         
> net.liftweb.http.LiftSession$$anonfun$processSurroundAndInclude$1$$anonfun$apply$57$$anonfun$apply$58$$anonfun$apply$59.apply(LiftSession.scala:1094)
>         net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
>         net.liftweb.http.S$.setVars(S.scala:1414)
>         
> net.liftweb.http.LiftSession$$anonfun$processSurroundAndInclude$1$$anonfun$apply$57$$anonfun$apply$58.apply(LiftSession.scala:1093)
>         
> net.liftweb.http.LiftSession$$anonfun$processSurroundAndInclude$1$$anonfun$apply$57$$anonfun$apply$58.apply(LiftSession.scala:1093)
>         net.liftweb.http.S$.withAttrs(S.scala:1433)
>         
> net.liftweb.http.LiftSession$$anonfun$processSurroundAndInclude$1$$anonfun$apply$57.apply(LiftSession.scala:1092)
>         
> net.liftweb.http.LiftSessi

[Lift] Re: 1.1-SNAPSHOT broken in Google App Engine

[Mark Tye]

I was able to confirm that clearing the cookie gets rid of the
ClassNotFoundException.

I have a hypothesis as to what happened: It appears that sometime
after the M4 milestone, the SessionToServletBridge moved from the
net.liftweb.http package to net.liftweb.http.provider.servlet. So, the
M4 version of my application serialized a
net.liftweb.http.SessionToServletBridge to a cookie, but the 1.1-
SNAPSHOT version couldn't find a class definition for the object when
deserializing the cookie and threw a ClassNotFoundException.

Anyway, problem resolved! Atsuhiko, thank you very much for your help!
David, thanks for bring the issue to Atsuhiko's attention!

- Mark

On Sep 1, 4:38 pm, Mark Tye  wrote:
> Thanks for taking a look at this issue. If the solution is as simple
> as clearing/removing a cookie, that's great news. I'll give it a try
> and let you know how it worked. Thanks again!
>
> - Mark
>
> On Aug 26, 2:57 am, Atsuhiko Yamanaka 
> wrote:
>
> > Hi,
>
> > On Mon, Aug 17, 2009 at 9:18 AM, Mark Tye wrote:
>
> > ...
>
> > > I don't know if compatibility with App Engine is a priority for the
> > > Lift team, but if this doesn't get fixed, I face an ugly choice
> > > between remaining frozen at 1.1-M4 as Lift development moves forward,
> > > or migrating away from App Engine to another cloud solution. Is there
> > > anything I can do to assist the diagnosis/resolution of this issue?
>
> > I have found that this problem will occur if you run lift app based on 
> > 1.1-M4
> > and then run lift app based on 1.1-SNAPSHOT.
> > And then, if you clear a cookie entry forhttp://yourapp.appsopt.com/
> > in your browser,
> > that problem will disappear.
>
> > I think there is not a solution in the 1.1-SNAPSHOT code.
>
> > How about clearing sessions before updating to 1.1-SNAPSHOT code base?
> > You know that sessions have been kept in the datastore and memcache,
> > and following code will clear them.
> > I have confirmed that I could cure that problem by following code
> > without deleting
> > a cookie in my browser.
>
> >   // clearing sessions in the datastore.
> >   import com.google.appengine.api.datastore.{Query,
> > DatastoreServiceFactory, Entity}
> >   implicit def foo(i:java.lang.Iterable[Entity]) = new Iterator[Entity]{
> >     val itt = i.iterator
> >     def hasNext:Boolean = itt.hasNext
> >     def next:Entity = itt.next
> >   }
> >   val datastore = DatastoreServiceFactory.getDatastoreService
> >   val results = datastore.prepare(new Query("_ah_SESSION"))
> >   for(session <- results.asIterable){
> >     datastore.delete(session.getKey())
> >   }
>
> >   // clearing memcache
> >   import java.util.Collections
> >   import javax.cache._
> >   val cacheFactory = CacheManager.getInstance.getCacheFactory
> >   val cache = cacheFactory.createCache(Collections.emptyMap())
> >   val stats = cache.getCacheStatistics
> >   cache.clear
>
> > Sincerely,
> > --
> > Atsuhiko Yamanaka
> > JCraft,Inc.
> > 1-14-20 HONCHO AOBA-KU,
> > SENDAI, MIYAGI 980-0014 Japan.
> > Tel +81-22-723-2150
> >     +1-415-578-3454
> > Skype callto://jcraft/
>
>

--~--~-~--~~~---~--~~
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 unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: 1.1-SNAPSHOT broken in Google App Engine

[Mark Tye]

I was able to confirm that clearing the cookie gets rid of the
ClassNotFoundException.

I have a hypothesis as to what happened: It appears that sometime
after the M4 milestone, the SessionToServletBridge moved from the
net.liftweb.http package to net.liftweb.http.provider.servlet. So, the
M4 version of my application serialized a
net.liftweb.http.SessionToServletBridge to a cookie, but the 1.1-
SNAPSHOT version couldn't find a class definition for the object when
deserializing the cookie and threw a ClassNotFoundException.

Anyway, problem resolved! Atsuhiko, thank you very much for your help!
David, thanks for bring the issue to Atsuhiko's attention!

- Mark


On Sep 1, 4:38 pm, Mark Tye  wrote:
> Thanks for taking a look at this issue. If the solution is as simple
> as clearing/removing a cookie, that's great news. I'll give it a try
> and let you know how it worked. Thanks again!
>
> - Mark
>
> On Aug 26, 2:57 am, Atsuhiko Yamanaka 
> wrote:
>
> > Hi,
>
> > On Mon, Aug 17, 2009 at 9:18 AM, Mark Tye wrote:
>
> > ...
>
> > > I don't know if compatibility with App Engine is a priority for the
> > > Lift team, but if this doesn't get fixed, I face an ugly choice
> > > between remaining frozen at 1.1-M4 as Lift development moves forward,
> > > or migrating away from App Engine to another cloud solution. Is there
> > > anything I can do to assist the diagnosis/resolution of this issue?
>
> > I have found that this problem will occur if you run lift app based on 
> > 1.1-M4
> > and then run lift app based on 1.1-SNAPSHOT.
> > And then, if you clear a cookie entry forhttp://yourapp.appsopt.com/
> > in your browser,
> > that problem will disappear.
>
> > I think there is not a solution in the 1.1-SNAPSHOT code.
>
> > How about clearing sessions before updating to 1.1-SNAPSHOT code base?
> > You know that sessions have been kept in the datastore and memcache,
> > and following code will clear them.
> > I have confirmed that I could cure that problem by following code
> > without deleting
> > a cookie in my browser.
>
> >   // clearing sessions in the datastore.
> >   import com.google.appengine.api.datastore.{Query,
> > DatastoreServiceFactory, Entity}
> >   implicit def foo(i:java.lang.Iterable[Entity]) = new Iterator[Entity]{
> >     val itt = i.iterator
> >     def hasNext:Boolean = itt.hasNext
> >     def next:Entity = itt.next
> >   }
> >   val datastore = DatastoreServiceFactory.getDatastoreService
> >   val results = datastore.prepare(new Query("_ah_SESSION"))
> >   for(session <- results.asIterable){
> >     datastore.delete(session.getKey())
> >   }
>
> >   // clearing memcache
> >   import java.util.Collections
> >   import javax.cache._
> >   val cacheFactory = CacheManager.getInstance.getCacheFactory
> >   val cache = cacheFactory.createCache(Collections.emptyMap())
> >   val stats = cache.getCacheStatistics
> >   cache.clear
>
> > Sincerely,
> > --
> > Atsuhiko Yamanaka
> > JCraft,Inc.
> > 1-14-20 HONCHO AOBA-KU,
> > SENDAI, MIYAGI 980-0014 Japan.
> > Tel +81-22-723-2150
> >     +1-415-578-3454
> > Skype callto://jcraft/
>
>

--~--~-~--~~~---~--~~
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 unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: 1.1-SNAPSHOT broken in Google App Engine

[Mark Tye]

Thanks for taking a look at this issue. If the solution is as simple
as clearing/removing a cookie, that's great news. I'll give it a try
and let you know how it worked. Thanks again!

- Mark

On Aug 26, 2:57 am, Atsuhiko Yamanaka 
wrote:
> Hi,
>
> On Mon, Aug 17, 2009 at 9:18 AM, Mark Tye wrote:
>
> ...
>
> > I don't know if compatibility with App Engine is a priority for the
> > Lift team, but if this doesn't get fixed, I face an ugly choice
> > between remaining frozen at 1.1-M4 as Lift development moves forward,
> > or migrating away from App Engine to another cloud solution. Is there
> > anything I can do to assist the diagnosis/resolution of this issue?
>
> I have found that this problem will occur if you run lift app based on 1.1-M4
> and then run lift app based on 1.1-SNAPSHOT.
> And then, if you clear a cookie entry forhttp://yourapp.appsopt.com/
> in your browser,
> that problem will disappear.
>
> I think there is not a solution in the 1.1-SNAPSHOT code.
>
> How about clearing sessions before updating to 1.1-SNAPSHOT code base?
> You know that sessions have been kept in the datastore and memcache,
> and following code will clear them.
> I have confirmed that I could cure that problem by following code
> without deleting
> a cookie in my browser.
>
>   // clearing sessions in the datastore.
>   import com.google.appengine.api.datastore.{Query,
> DatastoreServiceFactory, Entity}
>   implicit def foo(i:java.lang.Iterable[Entity]) = new Iterator[Entity]{
>     val itt = i.iterator
>     def hasNext:Boolean = itt.hasNext
>     def next:Entity = itt.next
>   }
>   val datastore = DatastoreServiceFactory.getDatastoreService
>   val results = datastore.prepare(new Query("_ah_SESSION"))
>   for(session <- results.asIterable){
>     datastore.delete(session.getKey())
>   }
>
>   // clearing memcache
>   import java.util.Collections
>   import javax.cache._
>   val cacheFactory = CacheManager.getInstance.getCacheFactory
>   val cache = cacheFactory.createCache(Collections.emptyMap())
>   val stats = cache.getCacheStatistics
>   cache.clear
>
> Sincerely,
> --
> Atsuhiko Yamanaka
> JCraft,Inc.
> 1-14-20 HONCHO AOBA-KU,
> SENDAI, MIYAGI 980-0014 Japan.
> Tel +81-22-723-2150
>     +1-415-578-3454
> Skype callto://jcraft/

--~--~-~--~~~---~--~~
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 unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: 1.1-SNAPSHOT issue?

[E. Biggs]

Many thanks!

--~--~-~--~~~---~--~~
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 unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: 1.1-SNAPSHOT issue?

[David Pollak]

Thanks.  Added a test.  Lift failed the test.  Fixed Lift.  Pushed the
source to GitHub.

On Thu, Aug 27, 2009 at 12:15 AM, E. Biggs  wrote:

>
> Ok here's the problem stripped down. The merge happens but the 
> node isn't being removed from the body
> Let me know if you'd like it in some other format.
>
> templates-hidden/outer.html:
>
> 
>  
>  
>  
>  
>
>  
> 
>
>
> inner.html:
>
> 
>  
>Inner
>  
> 
>
> renders:
>
> 
>  www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
> 
> 
>  
>
>
> Inner
>
>
>  script>
> 
> 
>
>  
>
>  
>
>
>
>