> > (p142, after a discussion of other cases)
> > "One very counterintuitive consequence of this unorthodox scoping rule
> > is illustrated by the following example: The result of the expression
>
> > select distinct sp.* from sp natural join s;
>
> > will include columns PNO and QTY but *not*
Thomas Lockhart <[EMAIL PROTECTED]> writes:
> (p142, after a discussion of other cases)
> "One very counterintuitive consequence of this unorthodox scoping rule
> is illustrated by the following example: The result of the expression
> select distinct sp.* from sp natural join s;
> will include
> I disagree on that. The table's real/alias name is certainly supposed
> to be accessible, and I see nothing in the spec that says that only some
> of its columns are accessible via qualification.
Date and Darwen disagree circa 1997, and I believe that SQL99 does not
radically alter the spec in
Peter Bierman <[EMAIL PROTECTED]> writes:
> At 3:16 PM -0500 12/16/00, Bruce Momjian wrote:
>> Here is the list of features in 7.1.
>> New Darwin/Mac OSX port (Bruce Hartzler)
> Not to be a snob, but I probably did 80% of this.
Bruce had submitted an earlier patch, but IIRC Peter's version was t
"Michael Richards" <[EMAIL PROTECTED]> writes:
> Sometimes the t_hoff value in the tuple header is 32 which seems to indicate
> no NULL bitmap.
There's no null bitmap unless the HASNULLS infomask bit is set.
> This really makes me wonder what happens when you ALTER
> TABLE ADD COLUMN on a table
This is because the first transaction has a lock on the
row in foo due to the references constrain, it currently
grabs the lock to prevent the pk row from being
removed after we tested its existance but before the transaction
closed. There's been talk about using some kind of dirty reads to dro
At 3:16 PM -0500 12/16/00, Bruce Momjian wrote:
>Here is the list of features in 7.1.
>New Darwin/Mac OSX port (Bruce Hartzler)
Not to be a snob, but I probably did 80% of this.
(BTW- tons of stuff at www.postgresql.org is busted. Searching mailing list archives
for example.)
-pmb
--
"Every t
I have just noticed that oper_select_candidate()'s first try at
resolving unknown-type inputs (parse_oper.c lines 372-410 in current
sources) is entirely redundant, because the case it is looking for
has already been tried by oper_exact(). I propose removing that
code, to make it more like func_s
We're working hardly on bugfixes for GiST (I've posted patch for 7.0.3)
and probably could finish in 1-2 weeks.
regards,
Oleg
On Sat, 16 Dec 2000, Bruce Momjian wrote:
> Date: Sat, 16 Dec 2000 15:16:22 -0500 (EST)
> From: Bruce Momjian <[EMAIL PROTECTED]>
> To: PostgreSQL
pg_attribute tells you the types and ordering of the attributes
(columns) of a table. Then see pg_type for the size and alignment
of each type.
regards, tom lane
> I'm not sure, but you may see some part of the NULL bitmap.
> IIRC it started at a quite illogical place, is suspect it was at byte 31
> but
> it still reserved 4bytes for each 32 fields after byte 32
Sometimes the t_hoff value in the tuple header is 32 which seems to indicate
no NULL bitmap. Th
Michael Richards wrote:
>
> > That's not right --- AFAIR there is no length in the tuple data. You
> > must use the length from the 'page item' pointer that points to this
> > tuple if you want to know the total tuple length.
>
> Oops, I meant attribute length...
>
> > If you were testing with
Here is the list of features in 7.1.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup.| Drexel Hill, Pennsylvania 19026
Rel
> That's not right --- AFAIR there is no length in the tuple data. You
> must use the length from the 'page item' pointer that points to this
> tuple if you want to know the total tuple length.
Oops, I meant attribute length...
> If you were testing with tables containing single varlena columns
Michael Richards wrote:
>
> Hi.
>
> I've still got something I can't seem to get. In my test cases with simple
> tables the first uint16 of tuple data after the header contained the length
> of the tuple. In this case I can't seem to figure out what the value F24D
> stands for when I'd expect it
"Michael Richards" <[EMAIL PROTECTED]> writes:
> I've still got something I can't seem to get. In my test cases with simple
> tables the first uint16 of tuple data after the header contained the length
> of the tuple.
That's not right --- AFAIR there is no length in the tuple data. You
must use
Hi.
I've still got something I can't seem to get. In my test cases with simple
tables the first uint16 of tuple data after the header contained the length
of the tuple. In this case I can't seem to figure out what the value F24D
stands for when I'd expect it's length to be 0800.
The first tuple
Did this work? If so, I'd like to add it to 7.1.
Peter Eisentraut writes:
> Arno A. Karner writes:
>
> > when i compile on linux i get shared libs, on sco with udk, or sdk just
> > get static libs
> > can some on point me to the config files to hack to get both static, and
> > shared libs
>
> T
"Rod Taylor" <[EMAIL PROTECTED]> writes:
> If you (collective core) feels that PostgreSQL has all the resources it req=
> uires at the moment, then please ignore this message.
Rod, I don't think the project has any need for full-up hosting as such,
but access to unusual platforms is frequently us
Thomas Lockhart <[EMAIL PROTECTED]> writes:
>> The first and second items here seem to be perfectly clear that the
>> names t1 and t2 have scope across the whole SELECT statement and are not
>> hidden within the formed by the OUTER JOIN clause.
> You are right. If there is a "correlation name",
hi, there!
test=> create table foo(id int primary key);
NOTICE: CREATE TABLE/PRIMARY KEY will create implicit index 'foo_pkey'
for table 'foo'
CREATE
test=> insert into foo values(1);
INSERT 88959 1
test=> create table bar(id int references foo);
NOTICE: CREATE TABLE will create implicit trigge
InQuent Technologies (www.inquent.com) has been using Postgresql for
quite a while now on various projects. It also has space in several large
data centres. After a brief discussion with my manager, it should be
feasible to offer a server and bandwidth to accomplish things which are needed
22 matches
Mail list logo
