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.
dave
_______________________________________________
gnucash-devel mailing list
[EMAIL PROTECTED]
http://www.gnumatic.com/cgi-bin/mailman/listinfo/gnucash-devel