Stefan Sturm wrote:
Hello,
I set up a PostgreSQL 8.3.1 Server on my Webserver( located somewhere
in the web ).
On my local Server I use the trust method to access the server. But on
my Webserver I want to use an user with password to access the Server.
So I did the following:
I created a use
am Fri, dem 18.04.2008, um 8:41:17 +0200 mailte Stefan Sturm folgendes:
> Hello,
>
> I set up a PostgreSQL 8.3.1 Server on my Webserver( located somewhere in the
> web ).
> On my local Server I use the trust method to access the server. But on my
> Webserver I want to use an user with password t
Hello,
I set up a PostgreSQL 8.3.1 Server on my Webserver( located somewhere in the
web ).
On my local Server I use the trust method to access the server. But on my
Webserver I want to use an user with password to access the Server.
So I did the following:
I created a user( as superuser ) with:
c
On Thu, 17 Apr 2008 16:43:04 -0400
Geoffrey <[EMAIL PROTECTED]> wrote:
> Joshua D. Drake wrote:
> > Hello,
> >
> > I am currently chilling at MySQLCon. If any other Elephant riders
> > who are doing a little Dolphin hunting are about... I am in
> > Ballroom E about to give a talk on what Mysql ca
On Thu, 17 Apr 2008 22:19:23 -0500
Josh Trutwin <[EMAIL PROTECTED]> wrote:
> Is your presentation available online at all?
Blogging the bad boy up right now Will be available soon.
Joshua D. Drake
--
The PostgreSQL Company since 1997: http://www.commandprompt.com/
PostgreSQL Community
On Thu, 17 Apr 2008 11:29:56 -0700
"Joshua D. Drake" <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I am currently chilling at MySQLCon. If any other Elephant riders
> who are doing a little Dolphin hunting are about... I am in
> Ballroom E about to give a talk on what Mysql can learn from
> PostgreSQL.
On Thursday 17 April 2008 19:32, Tom Lane wrote:
> Terry Lee Tucker <[EMAIL PROTECTED]> writes:
> > Didn't get any nibbles on this one. Can anybody provide any insight on
> > this?
>
> You're complaining in the wrong place ... I dunno what perlAPI.c is, but
> it's not part of Postgres.
>
> FWIW, pl
Terry Lee Tucker <[EMAIL PROTECTED]> writes:
> Didn't get any nibbles on this one. Can anybody provide any insight on this?
You're complaining in the wrong place ... I dunno what perlAPI.c is, but
it's not part of Postgres.
FWIW, plperl.c seems to work around the issue this way:
#include "postgr
On Thu, Apr 17, 2008 at 11:29 AM, Joshua D. Drake <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I am currently chilling at MySQLCon. If any other Elephant riders who
> are doing a little Dolphin hunting are about... I am in Ballroom E
> about to give a talk on what Mysql can learn from PostgreSQL.
is
Didn't get any nibbles on this one. Can anybody provide any insight on this?
Thanks...
On Thursday 17 April 2008 10:03, Terry Lee Tucker wrote:
> Greetings:
>
> We are converting from 7.4.19 to 8.3. While compiling our application using
> version 8.3, I have noticed the following warning from the
Joshua D. Drake wrote:
Hello,
I am currently chilling at MySQLCon. If any other Elephant riders who
are doing a little Dolphin hunting are about... I am in Ballroom E
about to give a talk on what Mysql can learn from PostgreSQL.
Check the room for barrels of tar and feathers before you start y
Dude, you have got to let us know how that goes...
On Apr 17, 2008, at 1:29 PM, Joshua D. Drake wrote:
Hello,
I am currently chilling at MySQLCon. If any other Elephant riders who
are doing a little Dolphin hunting are about... I am in Ballroom E
about to give a talk on what Mysql can learn fro
Hello,
I am currently chilling at MySQLCon. If any other Elephant riders who
are doing a little Dolphin hunting are about... I am in Ballroom E
about to give a talk on what Mysql can learn from PostgreSQL.
Sincerely,
Joshua D. Drake
--
The PostgreSQL Company since 1997: http://www.commandpromp
On Thu, Apr 17, 2008 at 1:55 PM, Roberts, Jon <[EMAIL PROTECTED]> wrote:
> Using the term "metadata" is misleading in your example. Metadata is
> data about data and in your example, you just have data. It is fine to
> join tables in an RDBMS.
>
I believe you missed the OP's actual goal. He's
> I have an existing table in an app, along the lines of:
> >>
> >> CREATE TABLE foo (
> >> name text,
> >> address text,
> >> some_numeric_info integer,
> >>
> >> );
> >>
>
>
> I essentially need another table
>
> CREATE TABLE foo_printing_options (
> field_name text,
> print_order int
[EMAIL PROTECTED] (Andrew Sullivan) writes:
> Oh, one other thing
>
> On Thu, Apr 17, 2008 at 12:44:51PM +0800, Craig Ringer wrote:
>
>> > One way I can think of doing it is to write a seen_log that notes what the
>> > client has already seen with a timestamp of (say) 1 minute. Then you can
>> >
Hello
UTF8 is supported from 8.2 version
Regards
Pavel Stehule
On 17/04/2008, Ottavio Campana <[EMAIL PROTECTED]> wrote:
> I created a database with locale [EMAIL PROTECTED], and I'm facing a weird
> problem
> with tsearch. Let me show it:
>
> tmptest=# SELECT * from pg_ts_cfg;
> ts_name
Mike Blackwell <[EMAIL PROTECTED]> writes:
> My question, then, is if it considered acceptable practice to, instead
> of having field_name in the secondary table, have a foreign key
> reference back to the field definition in the meta-data.
If you mean a foreign key reference into the system catal
More detail, as suggested.
I have an existing table in an app, along the lines of:
>>
>> CREATE TABLE foo (
>> name text,
>> address text,
>> some_numeric_info integer,
>>
>> );
>>
I essentially need another table
CREATE TABLE foo_printing_options (
field_name text,
print_order int not
I created a database with locale [EMAIL PROTECTED], and I'm facing a weird
problem with tsearch. Let me show it:
tmptest=# SELECT * from pg_ts_cfg;
ts_name | prs_name |locale
-+--+--
default_russian | default | ru_RU.KOI8-R
simple | de
On Apr 17, 2008, at 10:23 AM, Mike Blackwell wrote:
I have an existing table in an app, along the lines of:
CREATE TABLE foo (
name text,
address text,
some_numeric_info integer,
);
I now need to be able to associate additional information (e.g.
printing
order) with each field. Is it
Un saludo a todos. Pueden probar el siguiente script, el cual me funcionó
perfectamente bien para una "silent install" del PostgreSQL 8.1.10:
msiexec.exe /i postgresql-8.1-int.msi /log resultado.txt /qr
INTERNALLAUNCH=1 ADDLOCAL=server,psql,pgadmin,psqlodbc BASEDIR="c:\postgres"
CREATESERVICEUSER
I have an existing table in an app, along the lines of:
CREATE TABLE foo (
name text,
address text,
some_numeric_info integer,
);
I now need to be able to associate additional information (e.g. printing
order) with each field. Is it a bad idea to use the (fully qualified)
field name as
Forget about what I said .. I can see the IN and in table in pgadmin III ..
IN is the first one... sorry about that:-)
David
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Hi Adam,
Yes your right .. here is the output. The only thing is that in PGadminIII
I just see the "in" table
Thanks for your help anyway!
Have a good day
David
Welcome to psql 8.3.0, the PostgreSQL interactive terminal.
Type: \copyright for distribution terms
\h for help with SQL
>
> It worked Thanks!! But there is definitly something wrong with the
> error
> message I got (right?):
>
> reference=# alter table "IN" add column INDESCS VARCHAR[];
> ERROR: column "indescs" of relation "IN" already exists
>
I don't know, what do you see when you \d "IN" ?
When you use d
Are you sure?
\d "IN"
Let us know if you have OTHER table called IN.
When you use quotes you are making them case sensitive, so "in" != "IN"
!= "In" etc, etc
David Gagnon escribió:
Hi Adam,
It worked Thanks!! But there is definitly something wrong with the error
message I got (right?):
J Ottery wrote:
Thanks Craig for making me look like an idiot. I feel bad now.
You don't look like an idiot, you look like someone who has just learned
something. If we don't learn from our mistakes, then we are idiots... ;)
--
Until later, Geoffrey
Those who would give up essential Libert
Hi Adam,
It worked Thanks!! But there is definitly something wrong with the error
message I got (right?):
reference=# alter table "IN" add column INDESCS VARCHAR[];
ERROR: column "indescs" of relation "IN" already exists
Anyway I can workaround with what you gave me.
Thanks again
David
--
> Could you just have a look to the output below? I try to add a column
> to a
> table named "in" (I know "in" is a reserved keyword but the table
> exists and
> I cannot change it). Postgresql complains that the column already
> exist but
> it didn't. Am I doing something wrong ?
Try: ALTER T
I all,
Could you just have a look to the output below? I try to add a column to a
table named "in" (I know "in" is a reserved keyword but the table exists and
I cannot change it). Postgresql complains that the column already exist but
it didn't. Am I doing something wrong ?
Thanks to point me
Greetings:
We are converting from 7.4.19 to 8.3. While compiling our application using
version 8.3, I have noticed the following warning from the compiler when
compiling perlAPI.c:
gcc -ggdb -Wall -Wmissing-prototypes -Wmissing-declarations -fforce-addr
-DUNIX-DSTDERR_MSG -D_REENTRANT -D_GNU_
Thanks everyone for your very helpful comments. I'm setting up some spikes
to check performance and functionality of various alternatives.
Rob
On 16/04/2008, Greg Smith <[EMAIL PROTECTED]> wrote:
>
> On Wed, 16 Apr 2008, Rob Collins wrote:
>
> My client has a flawed MS SQL Server system
> >
>
>
am Thu, dem 17.04.2008, um 3:05:14 -0600 mailte kevin kempter folgendes:
> However in the 8.3.1 cluster I get this (Both clusters have the same
> data set - via a pg_dump):
>
> # select customer_srcid || segment_srcid from test_dim;
> ERROR: operator does not exist: bigint || bigint
> LINE 1:
kevin kempter wrote:
I have a table as follows:
\d test_dim
Table "public.test_dim"
Column |Type | Modifiers
-+-+
customer_srcid | bigint | not
I have a table as follows:
\d test_dim
Table "public.test_dim"
Column |Type | Modifiers
-+-+
customer_srcid | bigint | not null
segment_srcid
Hello,
thanks for your ansers.
PgSphere (http://pgfoundry.org/projects/pgsphere)
>
I think this look most promising. Is here someone using it and can give me
some tipps?
Thanks and greetings,
Stefan Sturm
On Wed, 2008-04-16 at 17:49 -0400, Chris Browne wrote:
> It would presumably not be _completely_ implausible to run a trigger
> when a table was ALTERed; the trouble would be in evaluating the
> semantics what OLD.* and NEW.* ought to contain, _if anything_.
Agreed.
If there was a simple use cas
My local firewall came up with a warning about postgres wanting to send
a network packet and I'm wondering if anyone can shed some light on its
trying to do?
The only line in pg_hba.conf that's not commented is
hostall all 127.0.0.1/32 trust
According to netstat -a
39 matches
Mail list logo
