On Fri, 2005-02-18 at 21:15, Stephan Szabo wrote:
> On Fri, 18 Feb 2005, Bret Hughes wrote:
>
> > I can't seem to find an explanation of what adding ONLY does for an sql
> > statement for instance :
> >
> > ALTER TABLE [ONLY] ADD COLUMN ...
> >
> > or what ever. Does anyone have a pointer to doc
On Fri, 18 Feb 2005, Bret Hughes wrote:
> I can't seem to find an explanation of what adding ONLY does for an sql
> statement for instance :
>
> ALTER TABLE [ONLY] ADD COLUMN ...
>
> or what ever. Does anyone have a pointer to docs on this. I am simply
> curious since there is obviously somethi
I can't seem to find an explanation of what adding ONLY does for an sql
statement for instance :
ALTER TABLE [ONLY] ADD COLUMN ...
or what ever. Does anyone have a pointer to docs on this. I am simply
curious since there is obviously something I am missing.
Bret
--
I did that and it did not work.
On the .net driver I had to do it on the connect string.
I also just tested latin and see the lower and upper do not work on the
French chars, while upper and lower do work on the French chars on a Unicode
database. So the problem is getting the odbc driver to work
On Feb 18, 2005, at 11:15 AM, Joel Fradkin wrote:
How do I tell the connection to use Unicode?
Try
SET client_encoding TO 'UNICODE';
http://www.postgresql.org/docs/8.0/interactive/sql-set.html
But it should default to the database encoding, so I'm not sure if that
is the problem.
John DeSoi, Ph.D
Looking deeper into the matter (which I admit I am a bit ignorant on) I
think you hit the nail on the head.
Coming from MSSQL which is using Latin I may have to use Latin1.
It works ok as SQL_ASCHII, but lower does not work, so hopefully using
LATIN1 I can store the chars and also get lower to work
Yea we examined it here as a group as we are facing the same kind of stuff
and found exactly the same thing.
It does what MSSQL called a Cartesian join, and ran no faster other then
removing the outer join logic.
Using a regular join statement and only inner joins was the same speed and I
think li
Hi Richard and group,
Thanks for the alternative approach. The code is certainly cleaner and
easier to follow, but I do have a couple outer joins for fields #2 and #3
that could contain null values that are not captured in your example.
Also, I ran an 'explain query' and the performance differe
I dont think it has anything to do with the data base as I can add fine
from pgadmin its an odbc question.
How do I tell the connection to use Unicode?
It worked ok using SQL_ASCHII also with the driver, but I thought if we get
a Chinese client down the road I couldnt store those chars unless i
Hi,
I use LATIN1 encoding and it works fine with accented characters. So try
creating your db with -E LATIN1 switch. Or even initdb -E LATIN1 if you wan't
your dbs default to that.
Best regards,
Aarni
On Friday 18 February 2005 16:59, you wrote:
> I wrote a program to read my database (from
I wrote a program to read my database (from MSSQL) and write it to Postgres.
It appeared to work great the first time I ran it, but the database was
SQL_ASCII (It defaulted to this when I created it from the command line on
the linux box using createdb.
When I tried to restore it I used PGAdmin on
Am Donnerstag, 17. Februar 2005 18:43 schrieb Michael Fuhr:
> SQL:2003 (Working Draft) says:
>
> Identify the triggers on tables in this catalog that are accessible
> to a given user or role.
>
> Apparently PostgreSQL implements the SQL:1999 specification of
> information_schema.triggers.
Whil
12 matches
Mail list logo
