On Tue, 29 Nov 2016, bto...@computer.org wrote:
The other bit of experience I'll share is the suggestion that invoicing is
a situation that lends itself to the uniformly incremented sequence
pattern. Accountants and comptrollers love this.
Reading your message brought to mind a suggestion
- Original Message -
> From: "rob" <r...@216software.com>
> To: pgsql-general@postgresql.org
> Sent: Tuesday, November 29, 2016 3:45:21 AM
> Subject: Re: [GENERAL] Invoice Table Design
>
> Hi Rich,
>
> thanks for the response -- going from M
rob wrote:
Hi Rich,
thanks for the response -- going from Mongo to Postgres does require the
kind of approach you suggest.
I suppose my question was a little bit more along the lines if anyone has
experience with designing payment / invoicing systems and any caveats they
may have encountered
Hi Rich,
thanks for the response -- going from Mongo to Postgres does require the
kind of approach you suggest.
I suppose my question was a little bit more along the lines if anyone has
experience with designing payment / invoicing systems and any caveats they
may have encountered along the way.
On Thu, 24 Nov 2016, Robert Heinen wrote:
A quick intro -- I'm helping a company switch from a mongo database over
to postgresql (yay!). The company is a marketplace app for musicians and
hosts. The basic idea is that a host can book a musician for an event,
like a wedding or a birthday. Also,
On Thu, Nov 24, 2016 at 9:17 AM, Robert Heinen wrote:
> I was wondering if anyone might be able to help me out with a table design
> question.
>
> A quick intro -- I'm helping a company switch from a mongo database over
> to postgresql (yay!). The company is a marketplace
I was wondering if anyone might be able to help me out with a table design
question.
A quick intro -- I'm helping a company switch from a mongo database over to
postgresql (yay!). The company is a marketplace app for musicians and
hosts. The basic idea is that a host can book a musician for an