That's a really good point about the create table, you can actually just
rename everything in you create table statements before you actually do
any data
import, then as long as the fields are in the same physical order(does
not matter if the names are different) you can output data from the
so
well, you could always write a little function that would loop through
every object and then rename to lower case and replace all spaces with _
underscores. Then in your application code just rename everything
accordingly.
Once again, even if you are using M$ SQL server it would be a good ide
On Wed, Jul 20, 2005 at 12:43:48PM +0100, teknokrat wrote:
> The problem we have is that we want to migrate to postgresql from our
> current sql server db, but the problem with caps requiring quotes around
> them makes this a far from easy migration.
The rule is pretty much, either always quote
# [EMAIL PROTECTED] / 2005-07-20 12:43:48 +0100:
> Tony Caduto wrote:
> >The easiest solution is just not to use caps or spaces in your
> >table/object names, there is no advantage to doing so.
> >People just need to get over the fact that having caps in a name make it
> >easier to read.
> >
> >M
Tony Caduto wrote:
The easiest solution is just not to use caps or spaces in your
table/object names, there is no advantage to doing so.
People just need to get over the fact that having caps in a name make it
easier to read.
My Test Table should be my_test_table, the naming makes no differe
Tony Caduto wrote:
> The easiest solution is just not to use caps or spaces in your
> table/object names, there is no advantage to doing so.
> People just need to get over the fact that having caps in a name make it
> easier to read.
>
> My Test Table should be my_test_table, the naming makes no
Tony Caduto wrote:
> The easiest solution is just not to use caps or spaces in your
> table/object names, there is no advantage to doing so.
> People just need to get over the fact that having caps in a name make it
> easier to read.
Not to pick nits, but I disagree. Capitalization (CamelCase in
p
The easiest solution is just not to use caps or spaces in your
table/object names, there is no advantage to doing so.
People just need to get over the fact that having caps in a name make it
easier to read.
My Test Table should be my_test_table, the naming makes no difference
to the applicat
How difficult would it be to add a configuration option (at the global,
database or session level) to make PostgreSQL transparently quote
identifiers for you? That would be a simple way to allow users to use
case-sensitive names without quoting everything manually or changing
deep parts of the back
You only need to use quotes in your SQL statements if your table names
in PostgreSQL contain any upper case letters. PostgreSQL automatically
converts all of your SQL statements to lower case unless they're quoted.
As an alternative to quoting in VB (assuming you're using Access as your
FE), stor
This is only really necessary if the table or column names are mixed cases or
include spaces or some such ... normally (?) this is not required. PostgreSQL
relentlessly lower cases such names unless they are double quoted.
HTH,
Greg Williamson
DBA
GlobeXplorer LLC
-Original Message-
F
11 matches
Mail list logo
