DB design document

[Phillip Shelton]

Ok. I have not had to use any database yet in my work so I have no real idea
about what is and is not available.

Phill

PS.

As a off-topic aside David M, I am enjoying the quotes in your sig.

> -----Original Message-----
> On Wed, Dec 13, 2000 at 06:41:34PM -0800, Dave Peticolas wrote:
> > David Merrill writes:
> > > On Thu, Dec 14, 2000 at 12:08:24PM +1000, Phillip Shelton wrote:
> > > >
> > > >
> > > > > -----Original Message-----
> > > > Do we need to worry about transaction_time here?
> > >
> > > I'm not sure about Postgres, but in Oracle a date field
> is really a
> > > date+time field. But I'll change the doc so it's obvious.
> >
> > GnuCash currently allows any date/time field to be set at nanosecond
> > resolution. It seems a bit overkill to me, so we might want to think
> > about dropping that, but it's something to keep in mind
> because right
> > now the api for it is there.
>
> We will be limited by the precision of the database. I'm not sure
> about Postgres' precision, but it is probably millisecond or so.