Use big int for time

Question

1.00/5 (2 votes)

See more:

Is it possible to use Big Int instead of Small Data

advantages and disadvantages

What I have tried:

C#

public long StartDate{get; set;}

public long EndDate{get; set;}

Posted 11-Aug-20 22:37pm

Member 14615938

Updated 12-Aug-20 4:55am

PIEBALDconsult

v2

Add a Solution

Comments

PIEBALDconsult 12-Aug-20 10:59am

Unless your application needs to interact with a system which uses ints, you're better off using DateTime or DateTimeOffset.
Time is not an integer.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2020-08-11T22:45:00

Well ... you could ... but unless you are interested in working with dates far, far away in the future or the past it's rather pointless. And even then, absolute precision isn't feasible so that kind of temporal distance probably doesn't need a ticks count, or even days - chances are that years are going to be less useful than millenia!
So why not just store the year in a long? A C# long is a 64 bit value, so it will hold the current age of the universe in 1/100th of seconds - going to a complicated type such as BigInt seems redundant.