"hubert depesz lubaczewski" <[EMAIL PROTECTED]> writes:
> On 3/19/07, Tom Lane <[EMAIL PROTECTED]> wrote:
>>> ERROR: WITH CHECK OPTION is not implemented
>> It seems perfectly clear to me ...
> errors is clear, but maybe the information about check option should
> be removed from docs to 8.2?
The
"Karthikeyan Sundaram" <[EMAIL PROTECTED]> writes:
>I am getting an error message:
> ERROR: WITH CHECK OPTION is not implemented
>what does this mean?
It seems perfectly clear to me ...
regards, tom lane
---(end of broadcast)--
Hi Everybody,
I have 2 versions of postgres 8.1.0 is my production version and 8.2.1
is my development version.
I am trying to create a view in my development version (8.2.3)
create view chnl_vw as select * from channel with check option;
I am getting an error message:
[Error] Scrip
Mark Simon wrote:
> create view things as select * from whatever;
>
> and then examine my saved view, I find a list of all of the fields
> from whatever. I thought it should be possible to save the star (*)
> as part of the view. Otherwise, I run into the problem of not getting
> all of the fie
I don't know whether this is a simple one that has been dealt with
before, but if so, I haven't worked out the right question to search on.
If I create a view thus:
create view things as select * from whatever;
and then examine my saved view, I find a list of all of the fields from
whate
- Original Message -
From: "Mario Splivalo" <[EMAIL PROTECTED]>
If you keep your definition in a script file, you can copy the script and
paste it into pgAdmin's Execute Arbitrary SQL Queries window, and then
execute the script from there.
It's still a pain. If I have two dozen vie
- Original Message -
From: "Mario Splivalo" <[EMAIL PROTECTED]>
Yes, I'm tied to the pgadmin3 for the moment, so there's nothing I could
do. It's a pain to develop a database such way.
Mario,
If you keep your definition in a script file, you can copy the script and
paste it into pg
On Tue, 2006-01-31 at 12:30 +, Richard Huxton wrote:
> Mario Splivalo wrote:
> > When I create a view, I like to define it like this (just representing
> > the form here):
> [snip]
> > But, when I extracit it from postgres, it's somehow stored like this:
> [snip]
> > The later is much more hard
Mario Splivalo wrote:
When I create a view, I like to define it like this (just representing
the form here):
[snip]
But, when I extracit it from postgres, it's somehow stored like this:
[snip]
The later is much more hard to read, and when I need to change the view,
i get rash and stuff :)
Is
When I create a view, I like to define it like this (just representing
the form here):
CREATE VIEW vw_my_view
AS
SELECT
t1.col1,
t2.col2
FROM
t1
JOIN t2
ON t1.col1 = t2.col3
WHERE
t2.col4 = 'bla'
But, when I extracit it from postgres, it's
On Wednesday 15 October 2003 02:01, Muhyiddin A.M Hayat wrote:
>
> Table Billing:
>
> id trx_date trx_time depart payment_method
> billing_amountamount_paid balance creator 1 10/09/2003
> 21:55:02 RestoVisa 13.
Dear all,
I Have This table
Table Billing:
id
trx_date trx_time depart payment_method
billing_amount amount_paid
balance creator
1 10/09/2003
21:55:02 Resto
Visa 13.800,00
Hi, Gary!
> CREATE
> create view loco_dets as
> select * from locos l
> left outer join
> (select * from lclass) lc on lc.lcid = l.lclass
> left outer join
(*) (select lnumber from lnumbers) ln on ln.lnid = l.lid and ln.lncurrent
> = true
> left outer join
>
On Monday 07 Jul 2003 4:10 pm, Gary Stainburn wrote:
> On Monday 07 Jul 2003 3:34 pm, Richard Huxton wrote:
> > Don't do "select *" do "select field_a,field_b..." - the * doesn't just
> > refer to the locos table.
>
> Sorry if I didn't make myself plain enough, but I had
>
> create view loco_dets a
On Monday 07 Jul 2003 3:34 pm, Richard Huxton wrote:
> On Monday 07 Jul 2003 2:12 pm, Gary Stainburn wrote:
> > I've managed to get the view I wanted by using sub-selects - as shown
> > below, but I now have the 'lid' field showing in the resulting view three
> > times (as lid, lnid and lnaid). Ho
On Monday 07 Jul 2003 2:12 pm, Gary Stainburn wrote:
>
> I've managed to get the view I wanted by using sub-selects - as shown
> below, but I now have the 'lid' field showing in the resulting view three
> times (as lid, lnid and lnaid). How can I remove lnid and lnaid from the
> result?
>
> create
On Monday 07 Jul 2003 1:36 pm, you wrote:
> On Monday 07 Jul 2003 1:07 pm, Richard Huxton wrote:
> > On Monday 07 Jul 2003 12:40 pm, Gary Stainburn wrote:
> > > left outer join
> > > (select lnumber from lnumbers) ln on ln.lnid = l.lid and
> >
> > ^^^
On Monday 07 Jul 2003 1:07 pm, Richard Huxton wrote:
> On Monday 07 Jul 2003 12:40 pm, Gary Stainburn wrote:
> > left outer join
> > (select lnumber from lnumbers) ln on ln.lnid = l.lid and
>
> ^^^ ^^^
>
> > ERROR: No such attribute or f
On Monday 07 Jul 2003 12:40 pm, Gary Stainburn wrote:
> left outer join
> (select lnumber from lnumbers) ln on ln.lnid = l.lid and
^^^ ^^^
> ERROR: No such attribute or function ln.lnid
Is is this?
--
Richard Huxton
-
On Mon, 7 Jul 2003, Gary Stainburn wrote:
> Hi folks,
>
> I know I'm missing something blindingly obvious, can someone point it out to
> me please.
>
> create table locos ( -- Locos table - contains details of locos
> lid int4 default nextval('loco_lid_seq'::text) unique not
Hi folks,
I know I'm missing something blindingly obvious, can someone point it out to
me please.
create table locos (-- Locos table - contains details of locos
lid int4 default nextval('loco_lid_seq'::text) unique not null,
lclass int4 references lclass(lcid),
Uz.ytkownik cio198 napisa?:
Hello,
i've created this table
CREATE TABLE "budget" (
"year" character varying NOT NULL,
"month" character varying NOT NULL,
"accountno" character varying NOT NULL,
"costid" character varying NOT NULL,
"valutacode" character va
[EMAIL PROTECTED] (cio198) writes:
> The problem is the numeric data in the view isn't limited to
> numeric(9,2) instead it become numeric(65535, 65531).
It should look like plain, unrestricted "numeric". Whatever is showing
you those bogus precision/scale fields is wrong. What client software
a
Hello,
i've created this table
CREATE TABLE "budget" (
"year" character varying NOT NULL,
"month" character varying NOT NULL,
"accountno" character varying NOT NULL,
"costid" character varying NOT NULL,
"valutacode" character varying,
"budgetvalue"
I found answer.
Thank you for everyone who did not reply.
CREATE VIEW depend_view AS
SELECT depend.subfunction_id, a.subfunction_file AS x,
depend.subfunction_dep_id, b.subfunction_file AS y
FROM depend INNER JOIN subfunction a ON depend.subfunction_id =
a.subfunction_id INNER JOIN subfunction b
> CREATE FUNCTION "requests_insert_after" () RETURNS opaque AS '
> DECLARE
> view_name text;
> BEGIN
> view_name := ''request_'' || NEW.id;
> CREATE VIEW view_name AS select * from groups;
> return NEW;
> END' LANGUAGE 'plpgsql';
>
> CREATE TRIGGER "requests_insert_aft
code
<<
CREATE FUNCTION "requests_insert_after" () RETURNS opaque AS '
DECLARE
view_name text;
BEGIN
view_name := ''request_'' || NEW.id;
CREATE VIEW view_name AS select * from groups;
return NEW;
END' LANGUAGE 'plpgsql';
CREATE TRIGGER "requests_insert_after"
Hi All,
I am trying to enable my web site to create views in a database owned by a
user called ddirpts. Now, the web server runs as nobody, and nobody has a
user and database set up in Postgres.. But the problem is, whenever I have a
cgi program issue a create view query on the ddirpts database,
28 matches
Mail list logo
