On Sun, Nov 12, 2006 at 02:21:10PM -0800, novnov wrote:
OK, thanks. I'm having a major internal debate about how I'm going to adjust
my habits to pgsql's 'lowercase is simplest' reality, all of this is
helpful.
Well, it's more like no quoting is simplest, then all the identifiers
are
I'm having a major internal debate about how I'm going to adjust
my habits to pgsql's 'lowercase is simplest' reality..
FYI, I adapted by going to quote everything. It takes getting used to, but
now I never have to worry about any keyword conflicts, ever, past present or
future. And I don't
OK, thanks. I'm having a major internal debate about how I'm going to adjust
my habits to pgsql's 'lowercase is simplest' reality, all of this is
helpful.
One thing I've not been able to determine is if there are any characters
besides the standard alphanumeric ones and _ that do not invoke the
Re this part of what you wrote:
For column names, I recommend using whatever is natural in the
decribing a field, irrespective of what the field is actually
pointing towards. For example, a table representing an object with a
creator attribute pointing to a user would have a column
On 11/8/06, novnov [EMAIL PROTECTED] wrote:
I am very curious to hear the various conventions folks here have arrived
at. I don't expect there to be consensus, but the various rationales might
help me arrive at an approach that works well for me.
Personally I use all lower caps names a typical
I'm new to pgsql, mostly coming from MSSQL. It sounds like it's simplest to
keep field names lowercase with pgsql, so I will have to change some habits
I've developed over the years. I would like to glean whatever collective
wisdom I can here from experienced pgsql devs.
I've been using
I've been using namestyles with mixed case like OrgID. That is much more
readable than orgid. Probably a good convention to adopt would be to use
namestyles like org_id. That change I can live with.
According to recommended practice you have a choice to make. Here is what
is described from the
Yes, I've already pretty much decided to use lowercase for all namestyles, I
mentioned that in the first post. Using lowercase invokes a set of other
issues, which I'm asking for options on...namely, conventions like org_id,
and emp_org_id, or simply using org_id as the fk pointer.
Richard
On Nov 8, 2006, at 18:49 , novnov wrote:
I've been using namestyles with mixed case like OrgID. That is much
more
readable than orgid. Probably a good convention to adopt would be
to use
namestyles like org_id. That change I can live with.
Both are perfectly acceptable, though the
On Wednesday November 8 2006 11:31 am, novnov wrote:
Yes, I've already pretty much decided to use lowercase for all
namestyles, I mentioned that in the first post. Using
lowercase invokes a set of other issues, which I'm asking for
options on...namely, conventions like org_id, and emp_org_id,
On 11/8/06, novnov [EMAIL PROTECTED] wrote:
I'm new to pgsql, mostly coming from MSSQL. It sounds like it's simplest to
keep field names lowercase with pgsql, so I will have to change some habits
I've developed over the years. I would like to glean whatever collective
wisdom I can here from
Merlin Moncure wrote:
looks much better than OrgID. I suggest not prefixing tables with
'tbl', but idx_ for indexes and fk_ for foreign keys is ok.
I've recently gotten into the habit of naming my indexes after
exactly what they index. For example:
create index foo(x,y,z) on foo(x,y,z);
and
Thanks that some good real world input. Not sure what it'll add up to for me
yet but good reference points.
In the db centric world I've been inhabiting for these years there are many
conventions re namestyles, they extend to table names, query names, field
names, variables, everything. I
13 matches
Mail list logo
