[thesite] Tips Database

[.jeff]

seth,

:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
: From: Seth Bienek
:
: > Sun, 19 Nov 2000 16:47:28 CST
: > Sun, 19 Nov 2000 16:47:28 +0300
: > Sun, 19 Nov 2000 16:47:28 +1000
: > Sun, 19 Nov 2000 16:47:28 -0800 (PST)
:
: Yeah, I was noticing that too.  What
: a bitch, eh?
:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

exactly.  if i were inclined and had to do it in cf, i'd be inclined to
create another structure called offsets where i'd use the abbreviations as
the keys and have the offset as the value:

<cfparam name="offsets" default="#StructNew()#">
<cfparam name="offsets.GMT" default="0000">
<cfparam name="offsets.CST" default="-0600">
<cfparam name="offsets.PST" default="-0800">

then you just gotta check the data type and match them up with the right
key, if necessary.

  offset: <cfif IsNumeric(ListGetAt(row, 6, " "))>
            #ListGetAt(row, 6, " ")#
          <cfelse>
            #offsets[ListGetAt(row, 6, " ")]#
          </cfif>

:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
: CST = Central Standard Time = -0600
: PST = Pacific Standard Time = -0800 (i think)
:
: There's like, 22 more of those, too...
:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

i think you're right about CST *not* being +/-0000.  after looking the data
over alittle better, i found some entries like this:

Sun, 19 Nov 2000 16:47:28 GMT

we *could* define all the possible offset abbreviations and map them to the
actual offset value, but i don't think that'll be necessary.  in my sampling
of over 4500 rows, i only found CST, GMT, and PST (which can be ignored
because it includes the offset in the same position as the rest of the
data).  so, that leaves CST and GMT abbreviations in the offset value column
that need to be dealt with.  of course, it doesn't hurt to take necessary
precautions either.  anybody got a listing of all offset abbreviations and
their values handy?

thanks,

.jeff

http://evolt.org/
jeff at members.evolt.org
http://members.evolt.org/jeff/