hi, I looking for SQL Server Management course in the Northern California
1-2 mo length. Please advise..
Thanks,
Dan Vanags
Isis New Media
(415) 885 5512
[EMAIL PROTECTED]
On Mon, Dec 18, 2000 at 12:32:54AM +0100, Thomas SMETS allegedly wrote:
> tsmets=> create sequence author_seq;
> CREATE
>
> tsmets=> create table author (
> tsmets=> author_id numeric primary key default
> nextval('author_seq'),
> tsmets=> name char(25) not null,
> tsmets=> surn
Hi,
In the long term I'm willing to construct a Little Java application that
runs a library. I was looking to create a few table & connect them
according to a non existing model . To create the Author table here's
what I thought doing for a table that should only contain The Name & the
Surname o
Hi all,
I've been running pgsql database since 6.3 with sizes ranging from a few
megabytes to a few hundred megabytes. And ever since 6.5 came out I've
had almost no crashes. Until now.
We recently installed a small server for an external party to develop
websites on. This machine, a K6-233 with
Frank Joerdens <[EMAIL PROTECTED]> writes:
> mpi=# update index set level = 2 where parentid = ( select id from
> index where level = 1 );
> ERROR: More than one tuple returned by a subselect used as an expression.
Apparently the subquery "select id from index where level = 1" is
returning more
Frank Joerdens wrote:
> mpi=# update index set level = 2 where parentid = ( select id from
> index where level = 1 );
> ERROR: More than one tuple returned by a subselect used as an
> expression. mpi=#
>
> This is a recursive query, on a single table. Is that not possible?
Hi Frank,
as the err
I am trying to do something that looks to me exactly like what's described in chapter
8.4
in the Postgresql book:
test=> UPDATE salesorder
test-> SET ship_date = '11/16/96'
test-> WHERE customer_id = (
test(> SELECT customer_id
test(> FROM customer
test(> WHERE name = 'Fleer Gearworks, Inc.'
tes
On Sat, Dec 16, 2000 at 06:39:14PM +0100, Peter Eisentraut wrote:
> Albert REINER writes:
>
> > I think that the documentation for CASE is not very clear:
>
> Maybe you will like this better (from upcoming 7.1):
>
> http://www.postgresql.org/devel-corner/docs/postgres/functions-conditional.htm
