That's actually helpful. Forgot about using the MySQL functions to narrow down the date/time like that.
As for your question: It's really going to be a function of what your user interface is -- you mentioned Excel, but then said it wasn't, and you also mentioned it's in a SQL table. I would assume that you'd use a 'date' field, so it's just a matter of dealing with the rest of it.
The input date/time formats will be decided by myself. The excel is just where I have the initial list of times. I do apologize for mentioning it. The problem with the Excel file is 1; parsing it. And 2; data's not guarentee concistant. So to get around this limitation, I'm creating my own data storeage format for this. I'm debating on storing a time with each day of the week or doing some M-F type storage and parsing that out. All one line? Multiple lines, etc...
-- philip
We put the 'K' in kwality!
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
