DB design document

[David Merrill]

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-----
> > > > Please take a look at the latest revision of my design document and
> > > > give me some feedback.
> > > > 
> > > > Some of the issues I'm dealing with:
> > > > 
> > > > 3. Table Schemas: Gaping holes.
> > > > I have quite a few questions about various fields that are marked with
> > > > question marks in the design document. Would you please take  look at
> > > > it and give me some feedback?
> > > 
> > > TRANSACTION
> > > -----------
> > > transaction_guid                char    32
> > > transaction_date                date            date of event
> > > notes                           varchar 50 (?)  anything the user enters
> > > 
> > > 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.

-- 
Dr. David C. Merrill                     http://www.lupercalia.net
Linux Documentation Project                dmerrill@lupercalia.net
Collection Editor & Coordinator            http://www.linuxdoc.org
                                       Finger me for my public key

work, n.:
	The blessed respite from screaming kids and
	soap operas for which you actually get paid.