I really appreciate all of the opinions on this. I've
been playing around with these different types in my sandbox. I've used
VBS, C#, VB.NET, and pretty much all of the languages that we hack programmers
use :)
The generalized date type worked really well. From
looking at the base AD schema it appears that there is a difference of opinion
among the MS programmers because the use of these different types is
roughly the same.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of joe
Sent: Tuesday, March 29, 2005 8:38 PM
To: [email protected]
Subject: RE: [ActiveDir] Storing dates in AD
If you use large int use filetime - Number 100
nanosecond intervals from jan 1, 1601. There is some docs (in fact I
think there are some typos in Gil's book) that mention the 1970 date but I am
not aware of anything in AD that uses anything but
filetime.
If you use int8 and don't use filetime, you will have
some developer hunt you down most likely later on because their generic
function that works on all other int8's doesn't work on
yours.
joe
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Isenhour, Joseph
Sent: Tuesday, March 29, 2005 4:06 PM
To: [email protected]
Subject: RE: [ActiveDir] Storing dates in AD
We are going to be modifying the field programmatically so
from what Gil said it sounds like the large integer method is appropriate.
As a follow up question, do you think I should use nano seconds from the Jan 2,
1970 (UNIX style) or January 1, 1601 (The date used by
pwdLastSet)?
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of joe
Sent: Monday, March 28, 2005 5:33 PM
To: [email protected]
Subject: RE: [ActiveDir] Storing dates in AD
Bingo, how is the data going to be used? I definitely
agree, don't come up with your own format unless you have some amazing scheme
that blows all of the other formats out of the water that makes it the best
thing to do. Not saying you aren't going to come up with something amazing but I
would guess the odds are against you. Anything you put into the directory, keep
it in UTC. Less confusion that way.
joe
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gil Kirkpatrick
Sent: Monday, March 28, 2005 3:44 PM
To: [email protected]
Subject: RE: [ActiveDir] Storing dates in AD
Depends on the domain of the date values, and how they are
used. If the dates will be passed along to other X.500/LDAP type directories,
you probably should use the Generalized Time syntax (2.5.5.11). If the dates are
manipulated programmatically, use the long integer representation. Its pretty
trivial to manipulate it as a date in your code. I'd avoid using a string
representation unless your code requires a funny string format or unless it
requires unusual date values like "today", "yesterday", or "when hell freezes
over" (we use the latter for setting development dates for certain silly feature
requests in our products :)
-gil
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Isenhour, Joseph
Sent: Monday, March 28, 2005 1:15 PM
To: [email protected]
Subject: [ActiveDir] Storing dates in AD
I'm looking for some opinions on a schema extension. I need to store a date type in AD. I figure I have several options.
Store it as a long integer. To determine the date the consumer will need to count the nano seconds from a certain date (the way that pwdLastSet works)
Store it as a date type (which I've never used, and looking at the current schema it appears that most people do not choose this option).
Store it as a unicode string and come up with a format like: YYYYMMDD[ss][ss]
Does anyone have an opinion on how this should be done?
Thanks
