At 11:15 -0600 11/14/02, Greg Macek wrote:
Thanks for the tip! Looks like I can change my date_archived field to
timestamp(8), since all I care about for this is the date information
(actual time is useless to me). My sql query all of a sudden got a lot
simpler. Thanks again for the help!
TIMEST
ally.
>
> Thanks,
>
> Matt
>
> Matthew P Baranowski
> Data Manager, Office of Educational Assessment
> University of Washington
>
> - Original Message -
> From: Greg Macek <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, N
Office of Educational Assessment
University of Washington
- Original Message -
From: Greg Macek <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, November 14, 2002 8:06 AM
Subject: INSERT INTO ... SELECT question
> Hello,
>
> I recently stumbled upon the INSERT IN
Well, amazingly enough, it works great! I found a test box to try it on
first before implementing this on the production box. This will
definitely make life easier...
On Thu, 2002-11-14 at 10:14, gerald_clark wrote:
> Did you try it?
> Did it work?
>
> Greg Macek wrote:
>
> >Hello,
> >
> >I rec
Hello,
I recently stumbled upon the INSERT INTO..SELECT abilities. Basically
what I'm doing is archiving records into another table before deleting
them (inventory information). However, I'd like to have the archive
table to have one more field than the original table: a date_archived
function. So
