IWETHEY v. 0.3.0 | TODO
1,095 registered users | 0 active users | 0 LpH | Statistics
Login | Create New User
IWETHEY Banner

Welcome to IWETHEY!

New Why not?

MS-SS doesn't like having two columns of type TIMESTAMP.


I've created (and needed) tables with multiple timestamp columns for years and have yet to run into any headaches using them. Granted, they were not huge tables - averaging 10K rows - but I'm not aware of anything in BOL advising to not have more than one TIMESTAMP column per table.
lincoln

"Chicago to my mind was the only place to be. ... I above all liked the city because it was filled with people all a-bustle, and the clatter of hooves and carriages, and with delivery wagons and drays and peddlers and the boom and clank of freight trains. And when those black clouds came sailing in from the west, pouring thunderstorms upon us so that you couldn't hear the cries or curses of humankind, I liked that best of all. Chicago could stand up to the worst God had to offer. I understood why it was built--a place for trade, of course, with railroads and ships and so on, but mostly to give all of us a magnitude of defiance that is not provided by one house on the plains. And the plains is where those storms come from." -- E.L. Doctorow


Never apply a Star Trek solution to a Babylon 5 problem.


I am not merely a "consumer" or a "taxpayer". I am a Citizen of the United States.


[link|mailto:bconnors@ev1.net|contact me]
New Re: Why not?
"A table can have only one timestamp column."

-- [link|http://msdn2.microsoft.com/en-us/ms182776(SQL.90).aspx|http://msdn2.microso...2776(SQL.90).aspx]

--
Chris Altmann
New They must mean system time via the database
Like I said, I've created many tables in the past with more than one timestamp column, all set programatically, and never had any problems.
lincoln

"Chicago to my mind was the only place to be. ... I above all liked the city because it was filled with people all a-bustle, and the clatter of hooves and carriages, and with delivery wagons and drays and peddlers and the boom and clank of freight trains. And when those black clouds came sailing in from the west, pouring thunderstorms upon us so that you couldn't hear the cries or curses of humankind, I liked that best of all. Chicago could stand up to the worst God had to offer. I understood why it was built--a place for trade, of course, with railroads and ships and so on, but mostly to give all of us a magnitude of defiance that is not provided by one house on the plains. And the plains is where those storms come from." -- E.L. Doctorow


Never apply a Star Trek solution to a Babylon 5 problem.


I am not merely a "consumer" or a "taxpayer". I am a Citizen of the United States.


[link|mailto:bconnors@ev1.net|contact me]
New TimeStamp is a non-standard type
In MS SQLServer, it is a system generated value. From the BOL:
Is a data type that exposes automatically generated, unique binary numbers within a database. timestamp is generally used as a mechanism for version-stamping table rows.
In other databases, it's more like a DATETIME value would be. Anyhow, you can't have two timestamp columns in MS SQLServer because they would be identical with each other. This automatically tells me that the SQL script above is not related to MS.
     Can anyone tell me what kind of SQL language this is? - (folkert) - (6)
         Looks like Sybase SQL Anywhere -NT - (admin)
         Pretty close to MS SQLServer - (ChrisR) - (4)
             Why not? - (lincoln) - (3)
                 Re: Why not? - (altmann) - (2)
                     They must mean system time via the database - (lincoln) - (1)
                         TimeStamp is a non-standard type - (ChrisR)

Wait 'til you sneeze, next.
40 ms