>
> Before continuing our Plans, I need to know how can I do with
> PostgreSQL in order to have Data Entry and Query Forms on clients side
> (How can I design Data Entry and Query Forms).
>
Hy. You could try using BOND framework which works for both linux and
win32. It is rather bad documented
Ah, I do think that sounds about like what I want! Let me play with this
one some, thanks so much!!
Richard Broersma Jr wrote:
Well, there is also: href="http://www.postgresql.org/docs/8.1/interactive/functions-comparisons.html#AEN13377";>
/expression/ /operator/ ANY (/array expression/). So,
Let's say I have a view like this:
CREATE VIEW v_small AS
SELECT c1, c2
FROM t1 JOIN t2 ON t1.c1 = t2.c2
and then I have another view
CREATE VIEW v_big AS
SELECT c1 FROM v_small WHERE c2 > 5
Now, when I do this:
SELECT * FROM v_big WHERE c1 < 1500
Is postgres going to make one query plan, or
On Jun 30, 2006, at 21:35 , Mario Splivalo wrote:
Is postgres going to make one query plan, or each view has it own
query
plan?
Have you taken a look at the EXPLAIN ANALYZE output of the queries?
You can see exactly which plan PostgreSQL will use.
Michael Glaesemann
grzm seespotcode net
On Fri, 2006-06-30 at 21:47 +0900, Michael Glaesemann wrote:
> On Jun 30, 2006, at 21:35 , Mario Splivalo wrote:
>
> > Is postgres going to make one query plan, or each view has it own
> > query
> > plan?
>
> Have you taken a look at the EXPLAIN ANALYZE output of the queries?
> You can see ex
Hi, Mario,
Mario Splivalo wrote:
>>> Is postgres going to make one query plan, or each view has it own
>>> query
>>> plan?
>> Have you taken a look at the EXPLAIN ANALYZE output of the queries?
>> You can see exactly which plan PostgreSQL will use.
>
> So, the performance will be the same if
I am practicing with SQL examples comming from the book:
JOE CELKO'S
SQL
PUZZLES
& ANSWERS
The following codes doesn't work on PostgreSQL 8.1.4 but according to the book
does conform to
SQL-92. Is there any other solutions that would result in the same effect? Or
is this an example
of a contr
> Also, I produced a second query using PostgreSQL:
> select a.id_i, a.ir_id, a.test, a.stamp
> from test a
> join
> (
> select max(stamp) as mstamp, id_i
> from test
> group by id_i
> ) b
> on a.stamp = b.mstamp
> where a.test = false
> ;
> -- result
> id_i | ir_id | test |stamp
> --
On Jul 1, 2006, at 6:55 , Richard Broersma Jr wrote:
CHECK ( 1 = ALL ( SELECT COUNT(STATUS)
FROM BADGES
WHERE STATUS = 'A'
GROUP BY EMPNO))
From the PostgreSQL docs (http://www.postgr
> > CHECK ( 1 = ALL ( SELECT COUNT(STATUS)
> > FROM BADGES
> > WHERE STATUS = 'A'
> > GROUP BY EMPNO))
>
> From the PostgreSQL docs (http://www.postgresql.org/docs/8.1/
> interactive/sql
Richard Broersma Jr <[EMAIL PROTECTED]> writes:
> The following codes doesn't work on PostgreSQL 8.1.4 but according to
> the book does conform to SQL-92.
> CHECK ( 1 = ALL ( SELECT COUNT(STATUS)
> FROM BADGES
> WHERE ST
> > The following codes doesn't work on PostgreSQL 8.1.4 but according to
> > the book does conform to SQL-92.
>
> > CHECK ( 1 = ALL ( SELECT COUNT(STATUS)
> > FROM BADGES
> > WHERE STATUS = 'A'
> >
12 matches
Mail list logo
