[Lift] Re: MappedDateTime losing time?
Derek Chen-Becker dchenbec...@gmail.com writes: OK, the fix has been pushed to 1.0.1-SNAPSHOT and it's in master (1.1-SNAPSHOT). Derek Excellent! Thanks /Jeppe --~--~-~--~~~---~--~~ 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: MappedDateTime losing time?
Yes, that should be fixed in both 1.1 and 1.0.1, really. I didn't even see that issue. The code freeze for 1.0.1 was yesterday, so if I want to get this fix in (which I think should be in there) then we'll need to push back 1.0.1. Let me send out a vote email. On Sun, Aug 23, 2009 at 12:27 PM, Jeppe Nejsum Madsen je...@ingolfs.dkwrote: Derek Chen-Becker dchenbec...@gmail.com writes: It should be very safe to use 1.0.1-SNAPSHOT. I'm planning on spinning the release of 1.0.1 GA next Wednesday, so we're in a code freeze starting Sunday. Really, the 1.0 line is strictly bug-fix at this point (1.1-SNAPSHOT is where new features make it in). So far, the things that have made it into 1.0.1 are: 1. Proper Oracle support 2. Fix for PostgreSQL double type 3. The DateTime fix 4. Some fixes for the Textile parser 5. Some minor XML parsing fixes (PCDataMarkupParser) 6. Some Actor fixes Derek, with the flurry of changes you're doing to the Db code (which is nice :-), it's increasingly difficult to maintain my own copy which fixes http://github.com/dpp/liftweb/issues#issue/36 Any chance to get this included in 1.1 soon? (It's a two line fix :-)? /Jeppe --~--~-~--~~~---~--~~ 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: MappedDateTime losing time?
OK, the fix has been pushed to 1.0.1-SNAPSHOT and it's in master (1.1-SNAPSHOT). Derek On Mon, Aug 24, 2009 at 1:30 PM, Derek Chen-Becker dchenbec...@gmail.comwrote: Yes, that should be fixed in both 1.1 and 1.0.1, really. I didn't even see that issue. The code freeze for 1.0.1 was yesterday, so if I want to get this fix in (which I think should be in there) then we'll need to push back 1.0.1. Let me send out a vote email. On Sun, Aug 23, 2009 at 12:27 PM, Jeppe Nejsum Madsen je...@ingolfs.dkwrote: Derek Chen-Becker dchenbec...@gmail.com writes: It should be very safe to use 1.0.1-SNAPSHOT. I'm planning on spinning the release of 1.0.1 GA next Wednesday, so we're in a code freeze starting Sunday. Really, the 1.0 line is strictly bug-fix at this point (1.1-SNAPSHOT is where new features make it in). So far, the things that have made it into 1.0.1 are: 1. Proper Oracle support 2. Fix for PostgreSQL double type 3. The DateTime fix 4. Some fixes for the Textile parser 5. Some minor XML parsing fixes (PCDataMarkupParser) 6. Some Actor fixes Derek, with the flurry of changes you're doing to the Db code (which is nice :-), it's increasingly difficult to maintain my own copy which fixes http://github.com/dpp/liftweb/issues#issue/36 Any chance to get this included in 1.1 soon? (It's a two line fix :-)? /Jeppe --~--~-~--~~~---~--~~ 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: MappedDateTime losing time?
Derek Chen-Becker dchenbec...@gmail.com writes: It should be very safe to use 1.0.1-SNAPSHOT. I'm planning on spinning the release of 1.0.1 GA next Wednesday, so we're in a code freeze starting Sunday. Really, the 1.0 line is strictly bug-fix at this point (1.1-SNAPSHOT is where new features make it in). So far, the things that have made it into 1.0.1 are: 1. Proper Oracle support 2. Fix for PostgreSQL double type 3. The DateTime fix 4. Some fixes for the Textile parser 5. Some minor XML parsing fixes (PCDataMarkupParser) 6. Some Actor fixes Derek, with the flurry of changes you're doing to the Db code (which is nice :-), it's increasingly difficult to maintain my own copy which fixes http://github.com/dpp/liftweb/issues#issue/36 Any chance to get this included in 1.1 soon? (It's a two line fix :-)? /Jeppe --~--~-~--~~~---~--~~ 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: MappedDateTime losing time?
On Thu, Aug 20, 2009 at 6:37 PM, Grant Wood smackt...@gmail.com wrote:
Hi David,
Here is the output you wanted:
-- Begin output
[INFO] Starting jetty 6.1.19 ...
2009-08-20 20:34:08.780::INFO: jetty-6.1.19
2009-08-20 20:34:08.908::INFO: No Transaction manager found - if your
webapp requires one, please configure one.
Date: 1 2009-08-20 00:00:00.0
2009-08-20 20:34:11.340::INFO: Started
selectchannelconnec...@0.0.0.0:8080
[INFO] Started Jetty Server
[INFO] Starting scanner at interval of 5 seconds.
You'll notice that the timestamps on startup are 20:34:11.340 but the
DateTest output was: 00:00:00.0
Yeah... it looks like a problem with the Derby driver...
Derek -- Did the fix to the Derby driver make it into 1.0.1?
Grant -- if you can use 1.1-SNAPSHOT or 1.1-M4, you'll have a fix to the
problem.
I hope this is helpful.
-Grant
On Aug 20, 11:38 am, David Pollak feeder.of.the.be...@gmail.com
wrote:
On Wed, Aug 19, 2009 at 10:14 PM, Grant Wood smackt...@gmail.com
wrote:
David,
I'm developing with Derby.
Please add this class:
import net.liftweb._
import mapper._
class DateTest extends LongKeyedMapper[DateTest] with IdPK {
def getSingleton = DateTest
object date extends MappedDateTime(this)
}
object DateTest extends DateTest with LongKeyedMetaMapper[DateTest]
And in boot, schemify DateTest and at the end of Boot, include the lines:
DateTest.create.date(now).save
for {
dt - DateTest.findAll()
} println(Date: +dt.id+ +dt.date.is)
Then send the output
I've been running Lift 1.0
-Grant
On Aug 19, 1:51 pm, David Pollak feeder.of.the.be...@gmail.com
wrote:
Grant,
What database are you using?
What version of Lift?
Thanks,
David
--
Lift, the simply functional web frameworkhttp://liftweb.net
Beginning Scalahttp://www.apress.com/book/view/1430219890
Follow me:http://twitter.com/dpp
Git some:http://github.com/dpp
--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp
--~--~-~--~~~---~--~~
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: MappedDateTime losing time?
I don't know that it did. Let me look into it.
On Fri, Aug 21, 2009 at 11:34 AM, David Pollak
feeder.of.the.be...@gmail.com wrote:
On Thu, Aug 20, 2009 at 6:37 PM, Grant Wood smackt...@gmail.com wrote:
Hi David,
Here is the output you wanted:
-- Begin output
[INFO] Starting jetty 6.1.19 ...
2009-08-20 20:34:08.780::INFO: jetty-6.1.19
2009-08-20 20:34:08.908::INFO: No Transaction manager found - if your
webapp requires one, please configure one.
Date: 1 2009-08-20 00:00:00.0
2009-08-20 20:34:11.340::INFO: Started
selectchannelconnec...@0.0.0.0:8080
[INFO] Started Jetty Server
[INFO] Starting scanner at interval of 5 seconds.
You'll notice that the timestamps on startup are 20:34:11.340 but the
DateTest output was: 00:00:00.0
Yeah... it looks like a problem with the Derby driver...
Derek -- Did the fix to the Derby driver make it into 1.0.1?
Grant -- if you can use 1.1-SNAPSHOT or 1.1-M4, you'll have a fix to the
problem.
I hope this is helpful.
-Grant
On Aug 20, 11:38 am, David Pollak feeder.of.the.be...@gmail.com
wrote:
On Wed, Aug 19, 2009 at 10:14 PM, Grant Wood smackt...@gmail.com
wrote:
David,
I'm developing with Derby.
Please add this class:
import net.liftweb._
import mapper._
class DateTest extends LongKeyedMapper[DateTest] with IdPK {
def getSingleton = DateTest
object date extends MappedDateTime(this)
}
object DateTest extends DateTest with LongKeyedMetaMapper[DateTest]
And in boot, schemify DateTest and at the end of Boot, include the
lines:
DateTest.create.date(now).save
for {
dt - DateTest.findAll()
} println(Date: +dt.id+ +dt.date.is)
Then send the output
I've been running Lift 1.0
-Grant
On Aug 19, 1:51 pm, David Pollak feeder.of.the.be...@gmail.com
wrote:
Grant,
What database are you using?
What version of Lift?
Thanks,
David
--
Lift, the simply functional web frameworkhttp://liftweb.net
Beginning Scalahttp://www.apress.com/book/view/1430219890
Follow me:http://twitter.com/dpp
Git some:http://github.com/dpp
--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp
--~--~-~--~~~---~--~~
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: MappedDateTime losing time?
It didn't. As soon as I get the PostgreSql patch pushed for 1.1-0SNAPSHOT
I'll work on getting the DateTime fix into 1.0.1
Derek
On Fri, Aug 21, 2009 at 2:57 PM, Derek Chen-Becker dchenbec...@gmail.comwrote:
I don't know that it did. Let me look into it.
On Fri, Aug 21, 2009 at 11:34 AM, David Pollak
feeder.of.the.be...@gmail.com wrote:
On Thu, Aug 20, 2009 at 6:37 PM, Grant Wood smackt...@gmail.com wrote:
Hi David,
Here is the output you wanted:
-- Begin output
[INFO] Starting jetty 6.1.19 ...
2009-08-20 20:34:08.780::INFO: jetty-6.1.19
2009-08-20 20:34:08.908::INFO: No Transaction manager found - if your
webapp requires one, please configure one.
Date: 1 2009-08-20 00:00:00.0
2009-08-20 20:34:11.340::INFO: Started
selectchannelconnec...@0.0.0.0:8080
[INFO] Started Jetty Server
[INFO] Starting scanner at interval of 5 seconds.
You'll notice that the timestamps on startup are 20:34:11.340 but the
DateTest output was: 00:00:00.0
Yeah... it looks like a problem with the Derby driver...
Derek -- Did the fix to the Derby driver make it into 1.0.1?
Grant -- if you can use 1.1-SNAPSHOT or 1.1-M4, you'll have a fix to the
problem.
I hope this is helpful.
-Grant
On Aug 20, 11:38 am, David Pollak feeder.of.the.be...@gmail.com
wrote:
On Wed, Aug 19, 2009 at 10:14 PM, Grant Wood smackt...@gmail.com
wrote:
David,
I'm developing with Derby.
Please add this class:
import net.liftweb._
import mapper._
class DateTest extends LongKeyedMapper[DateTest] with IdPK {
def getSingleton = DateTest
object date extends MappedDateTime(this)
}
object DateTest extends DateTest with LongKeyedMetaMapper[DateTest]
And in boot, schemify DateTest and at the end of Boot, include the
lines:
DateTest.create.date(now).save
for {
dt - DateTest.findAll()
} println(Date: +dt.id+ +dt.date.is)
Then send the output
I've been running Lift 1.0
-Grant
On Aug 19, 1:51 pm, David Pollak feeder.of.the.be...@gmail.com
wrote:
Grant,
What database are you using?
What version of Lift?
Thanks,
David
--
Lift, the simply functional web frameworkhttp://liftweb.net
Beginning Scalahttp://www.apress.com/book/view/1430219890
Follow me:http://twitter.com/dpp
Git some:http://github.com/dpp
--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp
--~--~-~--~~~---~--~~
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: MappedDateTime losing time?
OK, the patch is in 1.0.1-SNAPSHOT. Grant, can you test against
1.0.1-SNAPSHOT and make sure that it works for you?
Thanks,
Derek
On Fri, Aug 21, 2009 at 2:05 PM, Derek Chen-Becker dchenbec...@gmail.comwrote:
It didn't. As soon as I get the PostgreSql patch pushed for 1.1-0SNAPSHOT
I'll work on getting the DateTime fix into 1.0.1
Derek
On Fri, Aug 21, 2009 at 2:57 PM, Derek Chen-Becker
dchenbec...@gmail.comwrote:
I don't know that it did. Let me look into it.
On Fri, Aug 21, 2009 at 11:34 AM, David Pollak
feeder.of.the.be...@gmail.com wrote:
On Thu, Aug 20, 2009 at 6:37 PM, Grant Wood smackt...@gmail.com wrote:
Hi David,
Here is the output you wanted:
-- Begin output
[INFO] Starting jetty 6.1.19 ...
2009-08-20 20:34:08.780::INFO: jetty-6.1.19
2009-08-20 20:34:08.908::INFO: No Transaction manager found - if your
webapp requires one, please configure one.
Date: 1 2009-08-20 00:00:00.0
2009-08-20 20:34:11.340::INFO: Started
selectchannelconnec...@0.0.0.0:8080
[INFO] Started Jetty Server
[INFO] Starting scanner at interval of 5 seconds.
You'll notice that the timestamps on startup are 20:34:11.340 but the
DateTest output was: 00:00:00.0
Yeah... it looks like a problem with the Derby driver...
Derek -- Did the fix to the Derby driver make it into 1.0.1?
Grant -- if you can use 1.1-SNAPSHOT or 1.1-M4, you'll have a fix to the
problem.
I hope this is helpful.
-Grant
On Aug 20, 11:38 am, David Pollak feeder.of.the.be...@gmail.com
wrote:
On Wed, Aug 19, 2009 at 10:14 PM, Grant Wood smackt...@gmail.com
wrote:
David,
I'm developing with Derby.
Please add this class:
import net.liftweb._
import mapper._
class DateTest extends LongKeyedMapper[DateTest] with IdPK {
def getSingleton = DateTest
object date extends MappedDateTime(this)
}
object DateTest extends DateTest with LongKeyedMetaMapper[DateTest]
And in boot, schemify DateTest and at the end of Boot, include the
lines:
DateTest.create.date(now).save
for {
dt - DateTest.findAll()
} println(Date: +dt.id+ +dt.date.is)
Then send the output
I've been running Lift 1.0
-Grant
On Aug 19, 1:51 pm, David Pollak feeder.of.the.be...@gmail.com
wrote:
Grant,
What database are you using?
What version of Lift?
Thanks,
David
--
Lift, the simply functional web frameworkhttp://liftweb.net
Beginning Scalahttp://www.apress.com/book/view/1430219890
Follow me:http://twitter.com/dpp
Git some:http://github.com/dpp
--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp
--~--~-~--~~~---~--~~
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: MappedDateTime losing time?
Hello Derek,
I can confirm that 1.01-SNAPSHOT fixes the problem. Here is output
from my test instance from earlier.
--- Begin
[INFO] Starting jetty 6.1.19 ...
2009-08-21 19:40:16.410::INFO: jetty-6.1.19
2009-08-21 19:40:16.526::INFO: No Transaction manager found - if your
webapp requires one, please configure one.
Date: 1 2009-08-20 00:00:00.0
Date: 2 2009-08-21 19:40:18.319
2009-08-21 19:40:18.822::INFO: Started
selectchannelconnec...@0.0.0.0:8080
--- End
Date 1 was on 1.0 and Date 2 was on 1.01-SNAPSHOT
How safe is it to use 1.01-SNAPSHOT for daily development at this
point?
Thank you for the fix!
Grant
On Aug 21, 4:02 pm, Derek Chen-Becker dchenbec...@gmail.com wrote:
OK, the patch is in 1.0.1-SNAPSHOT. Grant, can you test against
1.0.1-SNAPSHOT and make sure that it works for you?
Thanks,
Derek
On Fri, Aug 21, 2009 at 2:05 PM, Derek Chen-Becker
dchenbec...@gmail.comwrote:
It didn't. As soon as I get the PostgreSql patch pushed for 1.1-0SNAPSHOT
I'll work on getting the DateTime fix into 1.0.1
Derek
On Fri, Aug 21, 2009 at 2:57 PM, Derek Chen-Becker
dchenbec...@gmail.comwrote:
I don't know that it did. Let me look into it.
On Fri, Aug 21, 2009 at 11:34 AM, David Pollak
feeder.of.the.be...@gmail.com wrote:
On Thu, Aug 20, 2009 at 6:37 PM, Grant Wood smackt...@gmail.com wrote:
Hi David,
Here is the output you wanted:
-- Begin output
[INFO] Starting jetty 6.1.19 ...
2009-08-20 20:34:08.780::INFO: jetty-6.1.19
2009-08-20 20:34:08.908::INFO: No Transaction manager found - if your
webapp requires one, please configure one.
Date: 1 2009-08-20 00:00:00.0
2009-08-20 20:34:11.340::INFO: Started
selectchannelconnec...@0.0.0.0:8080
[INFO] Started Jetty Server
[INFO] Starting scanner at interval of 5 seconds.
You'll notice that the timestamps on startup are 20:34:11.340 but the
DateTest output was: 00:00:00.0
Yeah... it looks like a problem with the Derby driver...
Derek -- Did the fix to the Derby driver make it into 1.0.1?
Grant -- if you can use 1.1-SNAPSHOT or 1.1-M4, you'll have a fix to the
problem.
I hope this is helpful.
-Grant
On Aug 20, 11:38 am, David Pollak feeder.of.the.be...@gmail.com
wrote:
On Wed, Aug 19, 2009 at 10:14 PM, Grant Wood smackt...@gmail.com
wrote:
David,
I'm developing with Derby.
Please add this class:
import net.liftweb._
import mapper._
class DateTest extends LongKeyedMapper[DateTest] with IdPK {
def getSingleton = DateTest
object date extends MappedDateTime(this)
}
object DateTest extends DateTest with LongKeyedMetaMapper[DateTest]
And in boot, schemify DateTest and at the end of Boot, include the
lines:
DateTest.create.date(now).save
for {
dt - DateTest.findAll()
} println(Date: +dt.id+ +dt.date.is)
Then send the output
I've been running Lift 1.0
-Grant
On Aug 19, 1:51 pm, David Pollak feeder.of.the.be...@gmail.com
wrote:
Grant,
What database are you using?
What version of Lift?
Thanks,
David
--
Lift, the simply functional web frameworkhttp://liftweb.net
Beginning Scalahttp://www.apress.com/book/view/1430219890
Follow me:http://twitter.com/dpp
Git some:http://github.com/dpp
--
Lift, the simply functional web frameworkhttp://liftweb.net
Beginning Scalahttp://www.apress.com/book/view/1430219890
Follow me:http://twitter.com/dpp
Git some:http://github.com/dpp
--~--~-~--~~~---~--~~
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: MappedDateTime losing time?
It should be very safe to use 1.0.1-SNAPSHOT. I'm planning on spinning the
release of 1.0.1 GA next Wednesday, so we're in a code freeze starting
Sunday. Really, the 1.0 line is strictly bug-fix at this point (1.1-SNAPSHOT
is where new features make it in). So far, the things that have made it into
1.0.1 are:
1. Proper Oracle support
2. Fix for PostgreSQL double type
3. The DateTime fix
4. Some fixes for the Textile parser
5. Some minor XML parsing fixes (PCDataMarkupParser)
6. Some Actor fixes
Technically speaking, the DateTime fix added MappedDate and MappedTime
classes so that people could choose what resolution they want on time
fields, but otherwise there isn't any new functionality.
Derek
On Fri, Aug 21, 2009 at 6:54 PM, Grant Wood smackt...@gmail.com wrote:
Hello Derek,
I can confirm that 1.01-SNAPSHOT fixes the problem. Here is output
from my test instance from earlier.
--- Begin
[INFO] Starting jetty 6.1.19 ...
2009-08-21 19:40:16.410::INFO: jetty-6.1.19
2009-08-21 19:40:16.526::INFO: No Transaction manager found - if your
webapp requires one, please configure one.
Date: 1 2009-08-20 00:00:00.0
Date: 2 2009-08-21 19:40:18.319
2009-08-21 19:40:18.822::INFO: Started
selectchannelconnec...@0.0.0.0:8080
--- End
Date 1 was on 1.0 and Date 2 was on 1.01-SNAPSHOT
How safe is it to use 1.01-SNAPSHOT for daily development at this
point?
Thank you for the fix!
Grant
On Aug 21, 4:02 pm, Derek Chen-Becker dchenbec...@gmail.com wrote:
OK, the patch is in 1.0.1-SNAPSHOT. Grant, can you test against
1.0.1-SNAPSHOT and make sure that it works for you?
Thanks,
Derek
On Fri, Aug 21, 2009 at 2:05 PM, Derek Chen-Becker
dchenbec...@gmail.comwrote:
It didn't. As soon as I get the PostgreSql patch pushed for
1.1-0SNAPSHOT
I'll work on getting the DateTime fix into 1.0.1
Derek
On Fri, Aug 21, 2009 at 2:57 PM, Derek Chen-Becker
dchenbec...@gmail.comwrote:
I don't know that it did. Let me look into it.
On Fri, Aug 21, 2009 at 11:34 AM, David Pollak
feeder.of.the.be...@gmail.com wrote:
On Thu, Aug 20, 2009 at 6:37 PM, Grant Wood smackt...@gmail.com
wrote:
Hi David,
Here is the output you wanted:
-- Begin output
[INFO] Starting jetty 6.1.19 ...
2009-08-20 20:34:08.780::INFO: jetty-6.1.19
2009-08-20 20:34:08.908::INFO: No Transaction manager found - if
your
webapp requires one, please configure one.
Date: 1 2009-08-20 00:00:00.0
2009-08-20 20:34:11.340::INFO: Started
selectchannelconnec...@0.0.0.0:8080
[INFO] Started Jetty Server
[INFO] Starting scanner at interval of 5 seconds.
You'll notice that the timestamps on startup are 20:34:11.340 but
the
DateTest output was: 00:00:00.0
Yeah... it looks like a problem with the Derby driver...
Derek -- Did the fix to the Derby driver make it into 1.0.1?
Grant -- if you can use 1.1-SNAPSHOT or 1.1-M4, you'll have a fix to
the
problem.
I hope this is helpful.
-Grant
On Aug 20, 11:38 am, David Pollak feeder.of.the.be...@gmail.com
wrote:
On Wed, Aug 19, 2009 at 10:14 PM, Grant Wood smackt...@gmail.com
wrote:
David,
I'm developing with Derby.
Please add this class:
import net.liftweb._
import mapper._
class DateTest extends LongKeyedMapper[DateTest] with IdPK {
def getSingleton = DateTest
object date extends MappedDateTime(this)
}
object DateTest extends DateTest with
LongKeyedMetaMapper[DateTest]
And in boot, schemify DateTest and at the end of Boot, include the
lines:
DateTest.create.date(now).save
for {
dt - DateTest.findAll()
} println(Date: +dt.id+ +dt.date.is)
Then send the output
I've been running Lift 1.0
-Grant
On Aug 19, 1:51 pm, David Pollak feeder.of.the.be...@gmail.com
wrote:
Grant,
What database are you using?
What version of Lift?
Thanks,
David
--
Lift, the simply functional web frameworkhttp://liftweb.net
Beginning Scalahttp://www.apress.com/book/view/1430219890
Follow me:http://twitter.com/dpp
Git some:http://github.com/dpp
--
Lift, the simply functional web frameworkhttp://liftweb.net
Beginning Scalahttp://www.apress.com/book/view/1430219890
Follow me:http://twitter.com/dpp
Git some:http://github.com/dpp
--~--~-~--~~~---~--~~
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: MappedDateTime losing time?
On Wed, Aug 19, 2009 at 10:14 PM, Grant Wood smackt...@gmail.com wrote:
David,
I'm developing with Derby.
Please add this class:
import net.liftweb._
import mapper._
class DateTest extends LongKeyedMapper[DateTest] with IdPK {
def getSingleton = DateTest
object date extends MappedDateTime(this)
}
object DateTest extends DateTest with LongKeyedMetaMapper[DateTest]
And in boot, schemify DateTest and at the end of Boot, include the lines:
DateTest.create.date(now).save
for {
dt - DateTest.findAll()
} println(Date: +dt.id+ +dt.date.is)
Then send the output
I've been running Lift 1.0
-Grant
On Aug 19, 1:51 pm, David Pollak feeder.of.the.be...@gmail.com
wrote:
Grant,
What database are you using?
What version of Lift?
Thanks,
David
--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp
--~--~-~--~~~---~--~~
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: MappedDateTime losing time?
Thanks, Grant, I'm glad to hear MappedTImestamp is useful. Please send me a Pull Request on GitHub if you have any general use code you think can be merged back in. Peter On Aug 19, 2:02 pm, Grant Wood smackt...@gmail.com wrote: Thank you Peter, In the process of trying to figure out the proper syntax to extend the MappedDateTime class I had run across your thread which had been very useful. After your comment, I grabbed your MappedTimestamp source from github and added code for my custom DateFormat. Works like a charm, thanks for the suggestion! Going line by line through the code, I'm not exactly sure how the minor differences between your class and Mine make it work properly, but I'm grateful that you contributed your code to community. As I become more comfortable with Scala it will hopefully become more clear. Thank You, and thanks to everyone who worked with you on it. Grant On Aug 19, 10:02 am, Peter Robinett pe...@bubblefoundry.com wrote: Hi Grant, I'm afraid I don't have the answer for you, but perhaps my attempt at making a MappedTimestamp will prove useful to you:http://groups.google.com/group/liftweb/msg/84b1612953fe9ac0. Peter Robinett --~--~-~--~~~---~--~~ 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: MappedDateTime losing time?
Hi David,
Here is the output you wanted:
-- Begin output
[INFO] Starting jetty 6.1.19 ...
2009-08-20 20:34:08.780::INFO: jetty-6.1.19
2009-08-20 20:34:08.908::INFO: No Transaction manager found - if your
webapp requires one, please configure one.
Date: 1 2009-08-20 00:00:00.0
2009-08-20 20:34:11.340::INFO: Started
selectchannelconnec...@0.0.0.0:8080
[INFO] Started Jetty Server
[INFO] Starting scanner at interval of 5 seconds.
You'll notice that the timestamps on startup are 20:34:11.340 but the
DateTest output was: 00:00:00.0
I hope this is helpful.
-Grant
On Aug 20, 11:38 am, David Pollak feeder.of.the.be...@gmail.com
wrote:
On Wed, Aug 19, 2009 at 10:14 PM, Grant Wood smackt...@gmail.com wrote:
David,
I'm developing with Derby.
Please add this class:
import net.liftweb._
import mapper._
class DateTest extends LongKeyedMapper[DateTest] with IdPK {
def getSingleton = DateTest
object date extends MappedDateTime(this)
}
object DateTest extends DateTest with LongKeyedMetaMapper[DateTest]
And in boot, schemify DateTest and at the end of Boot, include the lines:
DateTest.create.date(now).save
for {
dt - DateTest.findAll()
} println(Date: +dt.id+ +dt.date.is)
Then send the output
I've been running Lift 1.0
-Grant
On Aug 19, 1:51 pm, David Pollak feeder.of.the.be...@gmail.com
wrote:
Grant,
What database are you using?
What version of Lift?
Thanks,
David
--
Lift, the simply functional web frameworkhttp://liftweb.net
Beginning Scalahttp://www.apress.com/book/view/1430219890
Follow me:http://twitter.com/dpp
Git some:http://github.com/dpp
--~--~-~--~~~---~--~~
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: MappedDateTime losing time?
Hi Grant,
I'm afraid I don't have the answer for you, but perhaps my attempt at
making a MappedTimestamp will prove useful to you:
http://groups.google.com/group/liftweb/msg/84b1612953fe9ac0.
Peter Robinett
On Aug 18, 6:02 pm, Grant Wood smackt...@gmail.com wrote:
Hello,
I've extended MappedDateTime to override _toForm (to add a
class=datepicker) and set my own DateFormat for the input/output.
This is so that I could use a JQuerry datepicker which allows me to
set the time as well as the date. Everything is working on the
client, and the date with time is sent to the server fine, but upon
retrieval from the database time is being lost.
08/25/2009 01:45 pm is what _toForm got sent from the form
08/25/2009 12:00 AM is what asHtml is printing back out. Time is
always 12:00 AM
To me, it looks as if the date is having the time stripped off the
long value of the Date. Looking in the MappedDateTime source, I don't
see anything that looks like it affects the long value of the Date
other than toLong, which appears to only be used by asJsExp. (To be
sure I've overwritten toLong with no affect.)
MappedDateTime converts the Date into a Timestamp for the database to
store. I know there are issues with Timestamp stripping off nanos,
but I've never heard of them stripping off hours also.
Any help would be appreciated. Thank You!
Example source
follows:
class MyMappedDateTime[T:Mapper[T]](owner: T) extends MappedDateTime
[T](owner) {
...
// _toForm
override def _toForm: Box[NodeSeq] =
S.fmapFunc( {s: List[String] = printDateFormatter.parse(s(0))} )
{ funcName =
Full(input type='text' class={classValue} id={fieldId} name=
{funcName}
value={is match {case null = case s = printDate(s)}}/)
}
// asHtml
override def asHtml: Node = Text(is match {case null = case s =
printDate(s)})
//date format:
val printDateFormatter = new SimpleDateFormat(MM/dd/ hh:mm aa)
// format a given Date
def printDate(in: Date) : String = printDateFormatter.format(in)
...
}
--~--~-~--~~~---~--~~
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: MappedDateTime losing time?
Grant,
What database are you using?
What version of Lift?
Thanks,
David
On Tue, Aug 18, 2009 at 6:02 PM, Grant Wood smackt...@gmail.com wrote:
Hello,
I've extended MappedDateTime to override _toForm (to add a
class=datepicker) and set my own DateFormat for the input/output.
This is so that I could use a JQuerry datepicker which allows me to
set the time as well as the date. Everything is working on the
client, and the date with time is sent to the server fine, but upon
retrieval from the database time is being lost.
08/25/2009 01:45 pm is what _toForm got sent from the form
08/25/2009 12:00 AM is what asHtml is printing back out. Time is
always 12:00 AM
To me, it looks as if the date is having the time stripped off the
long value of the Date. Looking in the MappedDateTime source, I don't
see anything that looks like it affects the long value of the Date
other than toLong, which appears to only be used by asJsExp. (To be
sure I've overwritten toLong with no affect.)
MappedDateTime converts the Date into a Timestamp for the database to
store. I know there are issues with Timestamp stripping off nanos,
but I've never heard of them stripping off hours also.
Any help would be appreciated. Thank You!
Example source
follows:
class MyMappedDateTime[T:Mapper[T]](owner: T) extends MappedDateTime
[T](owner) {
...
// _toForm
override def _toForm: Box[NodeSeq] =
S.fmapFunc( {s: List[String] = printDateFormatter.parse(s(0))} )
{ funcName =
Full(input type='text' class={classValue} id={fieldId} name=
{funcName}
value={is match {case null = case s = printDate(s)}}/)
}
// asHtml
override def asHtml: Node = Text(is match {case null = case s =
printDate(s)})
//date format:
val printDateFormatter = new SimpleDateFormat(MM/dd/ hh:mm aa)
// format a given Date
def printDate(in: Date) : String = printDateFormatter.format(in)
...
}
--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp
--~--~-~--~~~---~--~~
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: MappedDateTime losing time?
Thank you Peter, In the process of trying to figure out the proper syntax to extend the MappedDateTime class I had run across your thread which had been very useful. After your comment, I grabbed your MappedTimestamp source from github and added code for my custom DateFormat. Works like a charm, thanks for the suggestion! Going line by line through the code, I'm not exactly sure how the minor differences between your class and Mine make it work properly, but I'm grateful that you contributed your code to community. As I become more comfortable with Scala it will hopefully become more clear. Thank You, and thanks to everyone who worked with you on it. Grant On Aug 19, 10:02 am, Peter Robinett pe...@bubblefoundry.com wrote: Hi Grant, I'm afraid I don't have the answer for you, but perhaps my attempt at making a MappedTimestamp will prove useful to you:http://groups.google.com/group/liftweb/msg/84b1612953fe9ac0. Peter Robinett --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
