Tony Caduto schrieb:
> I think a client that tells me the columns are a, b, c but then
>
>> gives me an error on "insert into table values (aval, bval, cval)"
>> because
>> the actual logical order is different is probably fairly broken.
>
>
> I guess that could be a problem, I was thinking in
I think a client that tells me the columns are a, b, c but then
gives me an error on "insert into table values (aval, bval, cval)" because
the actual logical order is different is probably fairly broken.
I guess that could be a problem, I was thinking in terms of how I do a
insert, I rarely d
On Sat, 21 Jan 2006, Tony Caduto wrote:
> Tom Lane wrote:
>
> > Please go back and read the very extensive discussions of this question
> > a couple years ago in the pghackers archives (around the time we were
> > implementing DROP COLUMN, iirc). There is no "just" about it.
>
> So it's a real bi
Tom Lane wrote:
Please go back and read the very extensive discussions of this question
a couple years ago in the pghackers archives (around the time we were
implementing DROP COLUMN, iirc). There is no "just" about it.
Maybe we need a easy button like in those Staples commercials :-)
So it'
On Wed, 18 Jan 2006, David Fetter wrote:
> On Wed, Jan 18, 2006 at 04:33:23PM -0800, Stephan Szabo wrote:
> > On Wed, 18 Jan 2006, Jim C. Nasby wrote:
> >
> > > Yeah, this isn't about production code, it's about making life
> > > easier on developers. Humans naturally want to group data into
> > >
Tony Caduto <[EMAIL PROTECTED]> writes:
>> It would definately be nice if the end-user concept of column order
>> wasn't tied to the physical order in the database.
> Ok this may be over simplistic, but we have a attnum for the physical
> order, why not just add a attorder and then we could just
> It would definately be nice if the end-user concept of column order
wasn't tied to the physical order in the database.
Ok this may be over simplistic, but we have a attnum for the physical
order, why not just add a attorder and then we could just change that
numbering and order by that fie
David Fetter <[EMAIL PROTECTED]> writes:
> Although it might be nice to have different column orderings, say
> per-role, the SQL:2003 standard requires a single canonical ordering
> in the information schema. How would we handle both?
If you want some other column ordering, you make a view. The
On Wed, Jan 18, 2006 at 04:33:23PM -0800, Stephan Szabo wrote:
> On Wed, 18 Jan 2006, Jim C. Nasby wrote:
>
> > Yeah, this isn't about production code, it's about making life
> > easier on developers. Humans naturally want to group data into
> > natural sets, so for example all the fields dealing
On Jan 19, 2006, at 9:10 , Jim C. Nasby wrote:
It would definately be nice if the end-user concept of column order
wasn't tied to the physical order in the database.
Tom Lane has mentioned at least a couple of times that decoupling the
(SQL-required) logical order from the physical order is
On Wed, 18 Jan 2006, Jim C. Nasby wrote:
> On Wed, Jan 18, 2006 at 08:10:07AM +0100, Joost Kraaijeveld wrote:
> > On Tue, 2006-01-17 at 09:52 -0800, David Fetter wrote:
> > > On Tue, Jan 17, 2006 at 10:28:03AM -0600, Tony Caduto wrote:
> > > > As long as we are talking wish lists...
> > > >
> > >
On Wed, Jan 18, 2006 at 08:10:07AM +0100, Joost Kraaijeveld wrote:
> On Tue, 2006-01-17 at 09:52 -0800, David Fetter wrote:
> > On Tue, Jan 17, 2006 at 10:28:03AM -0600, Tony Caduto wrote:
> > > As long as we are talking wish lists...
> > >
> > > What I would like to see is some way to change the
On Wed, 2006-01-18 at 10:10 +0100, Tino Wildenhain wrote:
> Joost Kraaijeveld schrieb:
> > On Tue, 2006-01-17 at 09:52 -0800, David Fetter wrote:
> >
> ...
> > Because a lot of tools that I use to manage a database during
> > *development* (e.g. PgAdmin) show the columns in an other order than the
Joost Kraaijeveld schrieb:
On Tue, 2006-01-17 at 09:52 -0800, David Fetter wrote:
...
Because a lot of tools that I use to manage a database during
*development* (e.g. PgAdmin) show the columns in an other order than the
order of attributes in my Java/C++ code. The "logical" order of the
colum
L.S.
I was afraid something like this would happen ;)
Just to be clear on the matter, the wrong post was just part of a conversation
between the OP and I. We are not exactly strangers and there was no
intentional nor accidential bad advice intended ;)
For the record I'll repeat on the list tha
As a service for the non-dutch speaking people, the abstract of Frank's
comment (hi Frank ;-)):
On Wed, 2006-01-18 at 09:10 +0100, ir. F.T.M. van Vugt bc. wrote:
> Op woensdag 18 januari 2006 08:10, schreef Joost Kraaijeveld:
> > Because a lot of tools that I use to manage a database during
> > *d
On Wed, Jan 18, 2006 at 09:10:23AM +0100, ir. F.T.M. van Vugt bc. wrote:
> Op woensdag 18 januari 2006 08:10, schreef Joost Kraaijeveld:
> > Because a lot of tools that I use to manage a database during
> > *development* (e.g. PgAdmin) show the columns in an other order than the
> > order of attrib
L.S.
Sorry 'bout that last post in dutch, it was meant to go to a private
address.
--
Best,
Frank.
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
Op woensdag 18 januari 2006 08:10, schreef Joost Kraaijeveld:
> Because a lot of tools that I use to manage a database during
> *development* (e.g. PgAdmin) show the columns in an other order than the
> order of attributes in my Java/C++ code. The "logical" order of the
> columns/attributes can cha
On Tue, 2006-01-17 at 09:52 -0800, David Fetter wrote:
> On Tue, Jan 17, 2006 at 10:28:03AM -0600, Tony Caduto wrote:
> > As long as we are talking wish lists...
> >
> > What I would like to see is some way to change the ordering of the
> > fields without having to drop and recreate the table.
>
[EMAIL PROTECTED] ("Jim C. Nasby") writes:
> On Tue, Jan 17, 2006 at 11:35:05AM -0500, Chris Browne wrote:
>>Note: I spent most of yesterday dealing with this very issue,
>>writing up a total of 31 eye-destroying regular expressions to
>>generate a pl/tcl function to parse cases that I
On Tue, Jan 17, 2006 at 11:35:05AM -0500, Chris Browne wrote:
>Note: I spent most of yesterday dealing with this very issue,
>writing up a total of 31 eye-destroying regular expressions to
>generate a pl/tcl function to parse cases that I had handy... I
>daresay that even with so m
> > > 8.
> > > The ability to use procedural-language extensions everywhere, not just
> > > in functions.
> >
> > Like where? Give an example.
>
> // PHP
> rows = pg_query('IF ... THEN ... ENDIF;');
>
// PHP
rows = pg_query('SELECT CASE WHEN ... ELSE ... END;');
--
Atentamente,
Jaime Casanova
(DB
On Tue, Jan 17, 2006 at 10:28:03AM -0600, Tony Caduto wrote:
> As long as we are talking wish lists...
>
> What I would like to see is some way to change the ordering of the
> fields without having to drop and recreate the table.
Why are you asking us to optimize the 'SELECT *' case which almost
[EMAIL PROTECTED] ("Jim C. Nasby") writes:
> On Mon, Jan 16, 2006 at 12:13:15PM -0500, Chris Browne wrote:
>> What you seem to be after, here, would confine your telno formatting
>> to telephone numbers for Canada and the United States, and would break
>> any time people have a need to express tele
On Mon, Jan 16, 2006 at 12:13:15PM -0500, Chris Browne wrote:
> What you seem to be after, here, would confine your telno formatting
> to telephone numbers for Canada and the United States, and would break
> any time people have a need to express telephone numbers outside those
> two countries.
>
"rlee0001" <[EMAIL PROTECTED]> writes:
>> > example. For example:
>> > In: 123 456-7890
>> > Out: (123) 456-7890
>> > Stored As:
>> >PHONE = (Virtual Function, with Regexp input parser)
>> >AREA_CODE = 123
>> >PREFIX = 456
>> >
Martijn van Oosterhout wrote:
> On Thu, Jan 12, 2006 at 08:51:44PM -0800, rlee0001 wrote:
> > 1.
> > Two new special variables in triggers functions (TG_STATEMENT and
> > TG_EFFECTIVE_STATEMENT) which returns the statement that triggered the
> > trigger.
>
> Which would that be? The statement that
On Fri, Jan 13, 2006 at 02:23:29PM +0100, Martijn van Oosterhout wrote:
> On Thu, Jan 12, 2006 at 08:51:44PM -0800, rlee0001 wrote:
> > 1.
> > Two new special variables in triggers functions (TG_STATEMENT and
> > TG_EFFECTIVE_STATEMENT) which returns the statement that triggered
> > the trigger.
>
Robert,
Others have covered some of your topics.
On Thu, 12 Jan 2006 20:51:44 -0800, rlee0001 wrote:
> 7.
> An XML field type and associated XPath/DOM functions. Other exotic
> field types like Image might be nice for some people as well. But XML
> would be awesome.
>
The contrib module xml2 (
On 1/13/06, Aly Dharshi <[EMAIL PROTECTED]> wrote:
>
> >
> >> 10.
> >> Or an alternative to views where tables can be defined with virtual
> >> fields which point to functions. So for example I can say:
> >> SELECT balance, name FROM customers WHERE balance < 0;
> >> ...where balance actu
You are wrong, you can make updatable views.
Yes you can but not out of the box. You have to write some rules to
make this go, isn't it ?
I think the point is that out of the box, yes you can create an
updateable view using rules.
You can not just say: create view and have it updatea
10.
Or an alternative to views where tables can be defined with virtual
fields which point to functions. So for example I can say:
SELECT balance, name FROM customers WHERE balance < 0;
...where balance actually performs a behind the scenes JOIN against a
transactions table and total
On Jan 13, 2006, at 8:47 AM, Michael Glaesemann wrote:
You can definitely cast boolean to integer:
The poster mentioned using PostgreSQL/PHP which may be the real
source of the issue. Boolean values are returned to PHP as strings
't' and 'f'. Of course, 'f' is not equivalent to FALSE in P
rlee0001 wrote:
2.
The ability to typecast from boolean to other datatypes. For example:
false::varchar
...would return varchar 'false' while:
Why should it return 'false'? If anything, it seems to me it should do
the same as this:
# select false;
bool
--
f
(1 row)
On Jan 13, 2006, at 13:51 , rlee0001 wrote:
I've been using PostgreSQL 8.1 with EMS PostgreSQL Manager and PHP for
about a month now and here are the top 10 features I'd like to see.
Keep in mind that I'm a novice so we might have some of this and I
just
can't find it in the docs.
There *i
On Thu, Jan 12, 2006 at 08:51:44PM -0800, rlee0001 wrote:
> 1.
> Two new special variables in triggers functions (TG_STATEMENT and
> TG_EFFECTIVE_STATEMENT) which returns the statement that triggered the
> trigger.
Which would that be? The statement that directly invoked the trigger,
or the one th
I've been using PostgreSQL 8.1 with EMS PostgreSQL Manager and PHP for
about a month now and here are the top 10 features I'd like to see.
Keep in mind that I'm a novice so we might have some of this and I just
can't find it in the docs.
1.
Two new special variables in triggers functions (TG_STATE
38 matches
Mail list logo
