> From: Chris Newbill [mailto:[EMAIL PROTECTED]]
> >snip... (been doing VBScript on ASP for several years, tho).
>
> I feel sorry for you. :)
;) Never fear. It works, does what it needs to do (so long as it's properly patched ;)
and
I make a fist-full of money for moon-lighting. Can't complain
-Original Message-
From: Tim Foster [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 25, 2001 8:19 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: [PHP-DEV] RE: [PHP-DB] PHP and MySQL queries...
>snip... (been doing VBScript on ASP for several years,
>tho).
I feel sorry f
RE: [PHP-DEV] RE: [PHP-DB] PHP and MySQL queries...Agreed.
Personally, I refuse to keep date values in fields that are not DATE fields
of some kind. Too much trouble.
TIM
-How do "Do Not Walk On Grass" signs get there?
-Original Message-
From: Robinson, Mike [mailto:[EMAIL
Title: RE: [PHP-DEV] RE: [PHP-DB] PHP and MySQL queries...
http://mysql.com/documentation/mysql/bychapter/manual_Reference.html#Date_and_time_types
Mysql permits all manner of formats for date/time storage,
and a whole slew of functions for retrieving date/time
info in useful, meaningful
y the overhead.
>>
>> FWIW, M$ likes to store their dates as two integers: one to hold the
>> date portion, the
>> other to hold the hours:minutes:seconds portion.
>>
>> If there's something about PHP/MySQL that makes this point moot,
>> please let me
seconds portion.
>
> If there's something about PHP/MySQL that makes this point moot, please
> let me know.
>
> TIM
> -He who always plows a straight furrow is in a rut.
>
>
>> -Original Message-
>> From: Mike Frazer [mailto:[EMAIL PROTECTED]]
>> Sent: Wednesday
kes this point moot, please let me know.
TIM
-He who always plows a straight furrow is in a rut.
> -Original Message-
> From: Mike Frazer [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, October 24, 2001 7:54 AM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: [PHP-DB]
Title: RE: [PHP-DEV] Re: [PHP-DB] PHP and MySQL queries...
In these days and times, conservation of a meg of disk
space is really not a consideration. Not the primary one anyway.
The data should be stored in a format such that the
storage itself and then retrieval can be executed with a
Agreed. This is especially useful when you need to conserve every byte you
can; a timestamp of "10/24/2001" or something similar is going to take 10
bytes as a string and an indeterminate number of bytes for an actual
timestamp because of system variations, whereas an integer value of 10242001
wi
Why don't you let them enter it however they want in the form
mm-dd-
mm/dd/yy
then in the php script that processes it, convert it with regulat expressions
to a timstamp and enter it in your database as an int. That's how I do it.
I don't understand the point in using the mysql timedate fiel
How about using 3 select menus:
* One for the day called 'dayselect'
* One for the month called 'monthselect;
* One for the year called 'yearselect'
When you get the values from the selects to perform query's upon, re-arrange the order
the dates
come in:
In your form they'll be in the order:
I am having a hard time setting up a form for users to enter a date in the
format of 00/00/ (of course they would use an actual date). My form is
as follows...
*I.E. - Format is 04/01/2001*
Search for Ads by date:
12 matches
Mail list logo
