Skip to Content.
Sympa Menu

freetds - Re: timestamps - a Stamping Problem? (Bus Error)

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Ian Struble" <iks AT callwave.com>
  • To: "TDS Development Group" <freetds AT franklin.oit.unc.edu>
  • Subject: Re: timestamps - a Stamping Problem? (Bus Error)
  • Date: Tue, 25 Apr 2000 13:48:32 -0700


I believe the correct name for retrieving the current time from a MS SQL is
CURRENT_TIMESTAMP.

> The name TIMESTAMP is deceptive. It's intended to generate a unique
> value and is not meant for retrieving the actual time.
>
> ----------
> From: Karl Pielorz[SMTP:kpielorz AT tdx.co.uk]
> Sent: Tuesday, April 25, 2000 4:02 PM
> To: TDS Development Group
> Subject: [freetds] Re: timestamps - a Stamping Problem? (Bus Error)
>
>
>
> Bob Kline wrote:
> >
> > On Tue, 25 Apr 2000, Karl Pielorz wrote:
> >
> > > [Questions about using the MS SQL Server TIMESTAMP.]
> >
> > Can't tell what's causing your bus error, but you should be aware of the
> > fact that Microsoft's TIMESTAMP has nothing whatsoever to do with the
> > standard SQL TIMESTAMP data type, nor indeed anything to do with the
> > current time.
>
> Now why, doesn't that actually suprise me? :)
>
> What ever format it is - it certainly causes FreeTDS to barf. If I get
time,
> I'll try and get a trace / more details etc.
>
> -Karl
>
> ---
> You are currently subscribed to freetds as: maraya-michael AT dol.gov
> To unsubscribe, forward this message to
> $subst('Email.Unsub')
>
>
> ---
> You are currently subscribed to freetds as: iks AT callwave.com
> To unsubscribe, forward this message to
$subst('Email.Unsub')
>
>





Archive powered by MHonArc 2.6.24.

Top of Page