On Wed, Jul 13, 2005 at 04:18:34PM -0400, Vivek Khera wrote:
I concur with this advice. Just use a sequence number which happens
to correspond with your software release numbers... or not. They can
be separate, especially once you get more stable and have more
software updaes than
On Thu, Jul 14, 2005 at 11:18:30AM +1000, Tim Allen wrote:
Others have given you some of the advice I would have given. One more
suggestion - does your database fit in just one schema in the gnumed
database?
It would, for the time being, size-wise. However, we have
conceptually separated the
Hi all,
we are developing GNUmed, a medical practice management
application running on PostgreSQL (you want your medical
data to be hosted by something reliable, don't you ;-) We
are putting out our first release sometime in the next two
weeks.
The idea is to name the production database
On Wed, Jul 13, 2005 at 05:56:03PM +0200, Karsten Hilbert wrote:
we are developing GNUmed, a medical practice management
application running on PostgreSQL (you want your medical
data to be hosted by something reliable, don't you ;-) We
are putting out our first release sometime in the next
On Wed, Jul 13, 2005 at 12:53:15PM -0400, Alvaro Herrera wrote:
we are developing GNUmed, a medical practice management
application running on PostgreSQL (you want your medical
data to be hosted by something reliable, don't you ;-) We
are putting out our first release sometime in the
On Wed, Jul 13, 2005 at 01:18:09PM -0400, Berend Tober wrote:
Or why bother including either? Just use sequential integers, maybe
left-padded with zeros to make the name the same length for the first
thousand or so releases?
A good tip, too, thanks. Would solve the ambiguity dilemma, too.
I
On Jul 13, 2005, at 1:18 PM, Berend Tober wrote:
Or why bother including either? Just use sequential integers, maybe
left-padded with zeros to make the name the same length for the
first thousand or so releases?
I concur with this advice. Just use a sequence number which happens
to
we are developing GNUmed, a medical practice management
application running on PostgreSQL (you want your medical
data to be hosted by something reliable, don't you ;-) We
are putting out our first release sometime in the next two
weeks.
The idea is to name the production database gnumed0.1 for
On Wed, Jul 13, 2005 at 01:21:01PM -0700, Philip Hallstrom wrote:
My main concern, however, was whether the *approach* is
sound, eg using a separate database name per release or IOW
version. One way would be to use the database name gnumed
regardless of release, another way would be to use
[EMAIL PROTECTED] wrote on 07/13/2005 02:59:02 PM:
On Wed, Jul 13, 2005 at 12:53:15PM -0400, Alvaro Herrera wrote:
we are developing GNUmed, a medical practice management
application running on PostgreSQL (you want your medical
data to be hosted by something reliable, don't you ;-)
Karsten Hilbert wrote:
My main concern, however, was whether the *approach* is
sound, eg using a separate database name per release or IOW
version. One way would be to use the database name gnumed
regardless of release, another way would be to use
gnumedX_Y for release X.Y. I wonder whether the
11 matches
Mail list logo
