How should I be thinking of intervals from a viewpoint of editing etc. eg TIMESTAMP I know its held in the database as a float but for editing purposes I present it as a string (or a date and a time separately). Should INTERVALS be presented as an integer or what?

Roy Lambert

Roy,

<< How should I be thinking of intervals from a viewpoint of editing etc. eg
TIMESTAMP I know its held in the database as a float but for editing
purposes I present it as a string (or a date and a time separately). >>

Actually, it's an Int64 in ElevateDB.  It's only a float in Delphi.

<< Should INTERVALS be presented as an integer or what? >>

Year-month intervals are integers, whereas day-time intervals are Int64s
internally in EDB:

http://www.elevatesoft.com/edb1d7_tedbyearmonthinterval.htm
http://www.elevatesoft.com/edb1d7_tedbdaytimeinterval.htm

You can use these methods of the TEDBEngine component to convert them to a
string as necessary:

http://www.elevatesoft.com/edb1d7_tedbengine_yearmonthintervaltosqlstr.htm
http://www.elevatesoft.com/edb1d7_tedbengine_daytimeintervaltosqlstr.htm

Or optionally you can just CAST() them to a string in the actual SQL
statement that you're using.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


1. Thanks
2. Wow Int64 some people are obviously going to have looooong intervals

Roy Lambert

Roy,

<< 2. Wow Int64 some people are obviously going to have looooong intervals
>>

It has to hold msecs, hence the need for a big value in some cases.  A year
in days isn't long, but it sure is when counted in msecs.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim

>It has to hold msecs, hence the need for a big value in some cases. A year
>in days isn't long, but it sure is when counted in msecs.

Or when trying to figure out new components

Roy Lambert

Roy,

<< Or when trying to figure out new components >>

Yes.

--
Tim Young
Elevate Software
www.elevatesoft.com