Running shoes last about 350 to 550 miles. This mostly depends on the surface(s) you run on, your weight, and your running style. Since I weigh a little more than the average runner and I run on asphalt and sidewalks my shoes are bald around 350 miles. Today I retired my Air Pegasus in favor of a sweet new pair of Nike Air Zoom HAYWARD (pictured above). The Hayward’s run a lot like my old Nike Air Zoom Moire’s.
For some reason when you have a datetime field in a cfgrid column it displays in a long format like this: Nov 17 2006 01:00:00
Fig 1 (Below) A date displayed in cfgrid
If we work a little SQL magic (using “CONVERT”) in the cfquery though we can do the formatting we want, which is: 11/17/2006. Refer to the “styles” listed in Figure 3 to see what formatting is available.
CONVERT(varchar,note_date,101) as note_date
ORDER BY note_date
Fig 2 (Below) A date displayed in cfgrid after using CONVERT in cfquery
Fig 3 (Below) A helpful list of “styles” to use with the SQL CONVERT function
|Style ID||Style Type|
|0 or 100||mon dd yyyy hh:miAM (or PM)|
|106||dd mon yy|
|107||Mon dd, yy|
|9 or 109||mon dd yyyy hh:mi:ss:mmmAM (or PM)|
|13 or 113||dd mon yyyy hh:mm:ss:mmm(24h)|
|20 or 120||yyyy-mm-dd hh:mi:ss(24h)|
|21 or 121||yyyy-mm-dd hh:mi:ss.mmm(24h)|
|126||yyyy-mm-dd Thh:mm:ss.mmm(no spaces)|
|130||dd mon yyyy hh:mi:ss:mmmAM|
Disclaimer: This tip will probably be really basic for most SQL folks.
The task: The company I work for has a web application that does some basic tracking of grants. The system feeding information to this application just had an across the board change to the numbering scheme of the grants. All grants must have a prefix of “999-”. Therefore, any grant not beginning with “999-” must be updated. Example: a grant with the current number 8789966 needs to be 999-8789966.
The solution: The SQL below does two things. It updates all the grants to prepend the 999- prefix while also skipping any grants that are already correctly prefixed.
SET grant_no = '999-' + grant_no
WHERE grant_no NOT LIKE '999-%'
I’ve had my Nike Amp + for several months so I’ve logged probably 300-400 miles with it. I’d say this qualifies me to finally pass my judgment on it. For anyone who
has gigantic, hulking biceps that are too large for standard arm bands would rather just put their iPod in their pocket this thing is the shiz.
In a nutshell, I dig it. But rather than be Nike’s promo boy, here’s my list o’ cons.
- You have to cut the band to custom fit your arm (rendering it useless to all your puny wristed friends). Come on Nike. You’re better than that.
- The watch function is only available at the press of a button.
- My wife tried controlling her nano with it for fun once and now when we run together it randomly controls both of our devices at times, which pisses her off. You have to keep explicitly unpairing them.
- The clasp is prone to unbuckling.