Ayende @ Rahien

Hi!
My name is Oren Eini
Founder of Hibernating Rhinos LTD and RavenDB.
You can reach me by phone or email:

ayende@ayende.com

+972 52-548-6969

, @ Q c

Posts: 5,972 | Comments: 44,520

filter by tags archive

Comments

Khalid Abuhakmeh

That makes sense. I just thought I was following a super secret Ayende on twitter and getting all your posts from the future. :P

jdn
jdn

This post is also showing up as a future post.

Thomas Levesque

I suspected it was related to timezones, because the posts eventually became accessible after a certain time... glad you fixed it!

James Manning

Not sure if it would have helped here, but FWIW I love using DateTimeOffset (added in 3.5 / SQL 2008) for reasons like this. Finally I don't have to worry about keeping everything UTC everywhere.

As Ferris would say: It is so choice. If you have the means, I highly recommend using it.

.NET side: http://msdn.microsoft.com/en-us/library/system.datetimeoffset.aspx

SQL side: http://msdn.microsoft.com/en-us/library/bb630289.aspx

Anders

I which we all could move to Zulu time (UTC) with no daylight saving. Imagine the global savings on software development!

Dmitry

Tags links on the right do not seem to work

Paul Stovell

This problem still exists.

Right now it is 11:38 AM GMT on 4 Jan 2012. In Google Reader a post appears titled "Embracing RavenDB" at http://ayende.com/blog/152707/embracing-ravendb

Google Reader displays:

Received: Jan 4, 2012 10:43 AM Published: Jan 4, 2012 10:00 AM

What's strange is that the post does not appear in your RSS feed anymore (view-source:http://ayende.com/blog/rss). It is as if the post was published long enough for Google Reader to pick it up, but then retracted.

Here is what your RSS feed looks like at 11:44 AM GMT:

https://gist.github.com/1559702

Why is Google Reader showing a post "published" at 10:43 AM that doesn't appear in your feed at 11:44 AM?

In any case, clicking on the post title in Google Reader displays a 404.

Paul

Ayende Rahien

Paul, Yes, but that stems from a different issue. I moved the post from time to time, but it didn't got moved correctly because of a different problem. Working on it now.

Comment preview

Comments have been closed on this topic.

FUTURE POSTS

  1. Reducing parsing costs in RavenDB - 8 hours from now

There are posts all the way to Aug 04, 2015

RECENT SERIES

  1. Production postmortem (5):
    29 Jul 2015 - The evil licensing code
  2. Career planning (6):
    24 Jul 2015 - The immortal choices aren't
  3. API Design (7):
    20 Jul 2015 - We’ll let the users sort it out
  4. What is new in RavenDB 3.5 (3):
    15 Jul 2015 - Exploring data in the dark
  5. The RavenDB Comic Strip (3):
    28 May 2015 - Part III – High availability & sleeping soundly
View all series

Syndication

Main feed Feed Stats
Comments feed   Comments Feed Stats