right. that's what we're saying. use datetime as the data type on the fields. timestamp CAN only be used in one place. datetime as many as you like.
christopher olive, cto, vp of web development cresco technologies, inc 410.825.0383 http://www.crescotech.com -----Original Message----- From: Tangorre, Michael T. [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 19, 2001 4:36 PM To: CF-Talk Subject: RE: CF and Time Yeah I get an error when tyring to save the tale, it says timestamp can only be used in one column. :-( -----Original Message----- From: Christopher Olive [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 19, 2001 4:28 PM To: CF-Talk Subject: RE: CF and Time that's strange. do you get an error when you try to assign more than one? christopher olive, cto, vp of web development cresco technologies, inc 410.825.0383 http://www.crescotech.com -----Original Message----- From: Tangorre, Michael T. [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 19, 2001 4:21 PM To: CF-Talk Subject: RE: CF and Time Hmmmm, But what if I want to send in 4 different times that are all being stored in the DB.. I am unable to use the datetime data type for all of the columns? -----Original Message----- From: Jon Hall [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 19, 2001 4:22 PM To: CF-Talk Subject: Re: CF and Time The timestamp datatype is an automatic timestamp for the record. That doesn't mean you cant have more than one timestamp though. You just have to do it manually. Create a column with a datetime datatype and set the default value to: getDate() Now when the record is created the default value will be a date/time stamp. When you want to update the time stamp just set the value to getDate() again. jon ----- Original Message ----- From: "Tangorre, Michael T." <[EMAIL PROTECTED]> To: "CF-Talk" <[EMAIL PROTECTED]> Sent: Wednesday, December 19, 2001 4:00 PM Subject: RE: CF and Time > Why can a SQL server Db table only contain one field of type > timestamp? I am not al that familiar with DBs yet. :-( > > Mike > > > -----Original Message----- > From: Bryan Love [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, December 19, 2001 3:45 PM > To: CF-Talk > Subject: RE: CF and Time > > > use timestamps. Timestamps are more versatile that varchars since you > can do math calculations with them. Depending on your gui layout you > may also > be better off storing a start time and a duration rather than a start > and > end time. > > Definitely use Timestamps - you'll thank yourself later when you write > the queries! > > +-----------------------------------------------+ > Bryan Love > Macromedia Certified Professional > Internet Application Developer > Database Analyst > Telecomunication Systems > [EMAIL PROTECTED] > +-----------------------------------------------+ > > "...'If there must be trouble, let it be in my day, that my child may > have peace'..." > - Thomas Paine, The American Crisis > > > > -----Original Message----- > From: Tangorre, Michael T. [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, December 19, 2001 12:35 PM > To: CF-Talk > Subject: CF and Time > > > Hi everyone. > > I am looking for the best way and data type (SQL) to store a employees > schedule. I have a form in which they enter a start time and an end > time. Should I > store these as Timestamps in SQL Server or use varchar... > And what about AM and PM? Any ideas would be much appreciated. > > Mike > > > Michael T. Tangorre > ======================== > Resident Assistant - Brick > Web Applications Developer > A.U. Webteam Slave :-) > AIM: CrazyFlash4====================== > > > > ______________________________________________________________________ Why Share? Dedicated Win 2000 Server � PIII 800 / 256 MB RAM / 40 GB HD / 20 GB MO/XFER Instant Activation � $99/Month � Free Setup http://www.pennyhost.com/redirect.cfm?adcode=coldfusionc FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
