• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: joda LocalDateTime
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: joda LocalDateTime


  • Subject: Re: joda LocalDateTime
  • From: Ramsey Gurley <email@hidden>
  • Date: Tue, 19 Nov 2013 14:43:02 -0700

On Nov 19, 2013, at 12:12 PM, Samuel Pelletier <email@hidden> wrote:

> The code in ValueFactory.java does nothing, a simple return new LocalDateTime(value) does the same thing.
>
> The problem with the LocalDateTime is the SQL timestamp is by definition an absolute point in time and that means it's calendar representation is time zone dependant.
>
> I think the LocalDate and LocalTime can work with my fix

LocalDate and DateTime works based on a modification of the test code I attached. Value in == value out. Feel free to simplify it if the Calendar stuff is not required. Just don’t break it :-) I use those two.

> but for LocalDateTime, I would need to add a double time zone adjustment to UTC or GMT; convert to UTC on save and from UTC on read.
>
> LocalDate and LocalTime seems more easily handled but I need to test.
>
> I try to avoid timestamp except for usage like log entry timestamp where we want to know when something occurred. For local time, I prefer string columns, their behaviour is always predictable.
>
> Samuel

I hate strings that need to conform to a certain format. It never fails. Someone always inserts something poorly formatted or a F'in magic string in the column.

is_active
“TRUE”
“FALSE”
“F”
“YES"
“MAYBE”

happy_hour
“18:00:00”
“99:99:99”
“noon"
“Gerald”
“CUSTOM"

I prefer to use the correct value type for the value being stored. Correct value types prevent all sorts of clever tricks. You see that preference of mine reflected in the existing prototypes. For postgres at least, the external types are the correct ones for the datastore. LocalTime uses time. LocalDate uses date. LocalDateTime and DateTime use timestamp. For other DBs, IDGAF so much :-)




 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden


  • Follow-Ups:
    • Re: joda LocalDateTime
      • From: Samuel Pelletier <email@hidden>
    • Re: joda LocalDateTime
      • From: David Avendasora <email@hidden>
References: 
 >joda LocalDateTime (From: Jeffrey Schmitz <email@hidden>)
 >Re: joda LocalDateTime (From: John Huss <email@hidden>)
 >Re: joda LocalDateTime (From: Samuel Pelletier <email@hidden>)
 >Re: joda LocalDateTime (From: Ramsey Gurley <email@hidden>)
 >Re: joda LocalDateTime (From: Samuel Pelletier <email@hidden>)

  • Prev by Date: ERJGroupsSynchronizer
  • Next by Date: Re: Horizontal inheritance between different models and different databases.
  • Previous by thread: Re: joda LocalDateTime
  • Next by thread: Re: joda LocalDateTime
  • Index(es):
    • Date
    • Thread