Thank you. Apparently I never saw this response, for some reason...
So reading that leaves me confused on one point, which is the right way to
do it if you're inserting an integer? would this be right? is there a
difference between the single and double quotes here?
(presume id is a bigint)
`ins
On Tue, Mar 7, 2017 at 1:29 PM, Pavel Stehule
wrote:
>
>
> 2017-03-07 21:04 GMT+01:00 Caleb Cushing :
>
>> Thank you. Apparently I never saw this response, for some reason...
>>
>> So reading that leaves me confused on one point, which is the right way
>> to do it if you're inserting an integer?
2017-03-07 21:04 GMT+01:00 Caleb Cushing :
> Thank you. Apparently I never saw this response, for some reason...
>
> So reading that leaves me confused on one point, which is the right way to
> do it if you're inserting an integer? would this be right? is there a
> difference between the single a
Hi
2017-02-21 15:19 GMT+01:00 Caleb Cushing :
> recently while exploring this problem http://stackoverflow.com/q/
> 40945277/206466. I decided to go with the docker container approach of a
> shell script.
>
> I realized that postgres' variables aren't quoted either, which results
> in me quoting
recently while exploring this problem
http://stackoverflow.com/q/40945277/206466. I decided to go with the docker
container approach of a shell script.
I realized that postgres' variables aren't quoted either, which results in
me quoting them with bash, to help avoid accidents, and even then I'm
On Sun, Nov 20, 2016 at 12:56 PM, Guillaume Lelarge
wrote:
> Le 18 nov. 2016 2:03 PM, "otheus uibk" a écrit :
>> Finally, if these changes can be implemented, is it impossible to backport
>> them to prior versions, say 9.1 and up? If I wrote a patch, under what
>> conditions would the patch be ac
Le 18 nov. 2016 2:03 PM, "otheus uibk" a écrit :
>
> A glaring weakness in Postgresql for production systems is that the
administrator has no way of controlling what types of logs go where. There
are at least two types of logs: errors and statement logs. (I could also
add: connection, syntax error
A glaring weakness in Postgresql for production systems is that the
administrator has no way of controlling what types of logs go where. There
are at least two types of logs: errors and statement logs. (I could also
add: connection, syntax error, query duration, audit). It has becomes
increasingly
On 12/9/2015 9:30 AM, Mirek Svoboda wrote:
Is it OK if I add feature request "faceting for FTS" to roadmap?
I hope you can define precisely what you mean by this in concrete terms,
as I look at it and scratch my head.
--
john r pierce, recycling bits in santa cruz
--
Sent via pgsql-g
On 12/9/15 11:30 AM, Mirek Svoboda wrote:
Is it OK if I add feature request "faceting for FTS" to roadmap?
If you're asking how to get a feature added to Postgres, you basically
have 4 options:
1) Convince an existing contributor to work on adding the feature.
2) Convince a large enough gro
Hello,
Is it OK if I add feature request "faceting for FTS" to roadmap?
Regards,
Mirek Svoboda | +420 608 224 486 | Skype: xsvobo10
On Tue, Jun 30, 2015 at 3:43 AM, Jeff Janes wrote:
> 2015-06-29 15:18 GMT-07:00 Bráulio Bhavamitra :
>>
>> Hello all,
>>
>> After reading
>> http://stackoverflow.com/questions/9407442/optimise-postgresql-for-fast-testing
>> I've tried to use commit_delay to make commits really slow on a test
>> en
2015-06-29 15:18 GMT-07:00 Bráulio Bhavamitra :
> Hello all,
>
> After reading
> http://stackoverflow.com/questions/9407442/optimise-postgresql-for-fast-testing
> I've tried to use commit_delay to make commits really slow on a test
> environment. Unfortunetely, the maximum value is 100ms (100_000
On Mon, Jun 29, 2015 at 7:43 PM, Tom Lane wrote:
> =?UTF-8?Q?Br=C3=A1ulio_Bhavamitra?= writes:
>> Besides increasing it, it would be great to have these two options
>> (fsync and commit_delay) per database, that is, valid only for
>> databases configured with them. That would greatly speed up tes
=?UTF-8?Q?Br=C3=A1ulio_Bhavamitra?= writes:
> Besides increasing it, it would be great to have these two options
> (fsync and commit_delay) per database, that is, valid only for
> databases configured with them. That would greatly speed up test
> running and still make the cluster available for ot
Hello all,
After reading
http://stackoverflow.com/questions/9407442/optimise-postgresql-for-fast-testing
I've tried to use commit_delay to make commits really slow on a test
environment. Unfortunetely, the maximum value is 100ms (100_000
microseconds).
Besides increasing it, it would be great to
Hi all;
We are running a multi-TB bioinformatics system on PostgreSQL and use a
denormalized schema in
places with a lot of tsvectors aggregated together for centralized
searching. This is
very important to the performance of the system. These aggregate many
documents (sometimes tens of thou
It would be nice if PostgreSQL has *_extend (similar to $.extend from
jQuery or _.extend from UnderscoreJs) for JSON/JSONB columns, so we could
write it like this:
UPDATE tablename
SET jsoncolumn = json_extend(jsoncolumn, $2)
WHERE id = $1;
instead of this:
UPDATE tablename
SET data = (
On 14 September 2014 22:01, cowwoc wrote:
> Hi,
>
> I'd like to propose the ability to create temporary schemas.
>
> Unlike temporary tables, this feature would enable developers to create a
> temporary schema once and execute CREATE TABLE statements without the
> TEMPORARY parameter.
>
I think
Hi guys,
I wanted to update you on this topic. Pete provided an excellent answer at
http://dba.stackexchange.com/a/76661/4719 that almost worked (we couldn't
find a solution for functions) but it turns out that my original problem
definition was incorrect.
I assumed that my unit tests only use on
On 14 September 2014 22:01, cowwoc wrote:
> Hi,
>
> I'd like to propose the ability to create temporary schemas.
>
> Unlike temporary tables, this feature would enable developers to create a
> temporary schema once and execute CREATE TABLE statements without the
> TEMPORARY parameter.
>
>
> I thi
On 09/15/2014 08:05 AM, cowwoc wrote:
On 15/09/2014 10:37 AM, Adrian Klaver wrote:
From your second post:
" 1. I'm already planning to run unit tests against a separate (but
identical) database than production, so there's no danger of wiping
out the production database.
2. I need to cr
On 15/09/2014 10:37 AM, Adrian Klaver wrote:
From your second post:
" 1. I'm already planning to run unit tests against a separate (but
identical) database than production, so there's no danger of wiping
out the production database.
2. I need to create a new temporary schema per test, a
On 09/15/2014 07:08 AM, cowwoc wrote:
On 15/09/2014 9:39 AM, Adrian Klaver wrote:
Not exactly. Each test is responsible for populating its own schema
(creating tables, inserting data). The main purpose of using temporary
schemas is to ensure that each test runs in isolation so that data from
ot
Interesting enough concept. Please don't forget to test against a realistic
data set as well. It does seem to me that the devs can easily make, fill, clean
up their own db. And a central builder (eg Jenkins?) can do the same with,
importantly using ALL tests.
Then again using real data.
> On
On 15/09/2014 9:39 AM, Adrian Klaver wrote:
Not exactly. Each test is responsible for populating its own schema
(creating tables, inserting data). The main purpose of using temporary
schemas is to ensure that each test runs in isolation so that data from
other tests cannot influence the outcome
On 09/14/2014 08:21 PM, cowwoc wrote:
Hi Adrian,
Replies below.
On 14/09/2014 8:34 PM, Adrian Klaver wrote:
On 09/14/2014 02:01 PM, cowwoc wrote:
See http://dba.stackexchange.com/q/76494/4719 for a related discussion.
So from the above link and the discussion here so far I gather you want:
Hi Adrian,
Replies below.
On 14/09/2014 8:34 PM, Adrian Klaver wrote:
On 09/14/2014 02:01 PM, cowwoc wrote:
See http://dba.stackexchange.com/q/76494/4719 for a related discussion.
So from the above link and the discussion here so far I gather you want:
1) A CREATE TEMPORARY SCHEMA that behav
On 09/14/2014 02:01 PM, cowwoc wrote:
Hi,
I'd like to propose the ability to create temporary schemas.
Unlike temporary tables, this feature would enable developers to create a
temporary schema once and execute CREATE TABLE statements without the
TEMPORARY parameter.
This would facilitate runn
On September 14, 2014 6:01:15 PM EDT, cowwoc wrote:
>
>On 14/09/2014 5:52 PM, Nick Guenther [via PostgreSQL] wrote:
>>
>>
>> On September 14, 2014 5:01:54 PM EDT, cowwoc <[hidden email]
>> > wrote:
>> >Hi,
>> >
>> >I'd like to propose the ability to create temporary schemas.
>> >
>> >This would
Hi Nick,
I don't think this would help for three reasons:
1. I'm already planning to run unit tests against a separate (but
identical) database than production, so there's no danger of wiping
out the production database.
2. I need to create a new temporary schema per test, and run 4-10
On September 14, 2014 5:01:54 PM EDT, cowwoc wrote:
>Hi,
>
>I'd like to propose the ability to create temporary schemas.
>
>This would facilitate running unit tests, where developers would like
>to run
>the same creation script for unit tests and production code but do not
What if you ran a tem
Hi,
I'd like to propose the ability to create temporary schemas.
Unlike temporary tables, this feature would enable developers to create a
temporary schema once and execute CREATE TABLE statements without the
TEMPORARY parameter.
This would facilitate running unit tests, where developers would l
> it would be great if i could simply write 'insert into simple_view returning
> col1' or 'insert into simple_view returning col2' and postgres would make the
> magic behind.
You can do it with 9.3~ servers already. Here is an example:
=# create table aa (a int);
CREATE TABLE
=# insert into aa va
hi all,
the automatic update for views is really a helpful feature, but i think it
would be more useful with returning support.
currently we have to construct a rule/trigger to support queries like
'insert into simple_view returning pk'
is it possible (or desired) to implement something like an
Hi all...
Forgive me if this is not the correct forum for such suggestions.
I'm about to begin using the custom format options for pg_restore, so that
we can leverage the performance gains from --jobs options.
However I would like to be able to specify the tablespace for individual
tables/indexes
Great thanks. I see there is talk of 9.3 including autonomous transaction
support as well.
-Original Message-
From: Kevin Grittner [mailto:kevin.gritt...@wicourts.gov]
Sent: Tuesday, August 07, 2012 1:04 PM
To: David Greco; pgsql-general@postgresql.org
Subject: Re: [GENERAL] Feature
Kevin Grittner wrote:
> David Greco wrote:
>
> > Surprised to see this isn't offered as a Foreign Data Wrapper- one
> > to other Postgres servers.
>
> People have been working on it. It seems quite likely to be
> included in the 9.3 release next year.
That's cool ;-)
Andreas
--
Really,
David Greco wrote:
> Surprised to see this isn't offered as a Foreign Data Wrapper- one
> to other Postgres servers.
People have been working on it. It seems quite likely to be
included in the 9.3 release next year.
-Kevin
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.o
Surprised to see this isn't offered as a Foreign Data Wrapper- one to other
Postgres servers. I was attempting to replace some uses I have of dbilink, and
found a couple places where I am using it to connect to Postgres. One is for
pseudo "Autonomous Transactions"- a db link to the same postgres
Hi.
I think that in specific statement with many constants:
CASE x
WHEN const1 THEN action1
WHEN const2 THEN action2
WHEN const3 THEN action3
WHEN const4 THEN action4
END CASE;
constants may be sorted at compile time, and when executed ,
it will be possible internally to use fast search:
Hi Daniel,
> Now I wanted to delete about 10 million addresses (that are not
> referenced anymore from anywhere), and have a statement like:
What about:
DELETE FROM address
WHERE id IN (
SELECT id FROM address
EXCEPT
(
SELECT address_id FROM tab1
UNION AL
2011/12/19 Marti Raudsepp :
> On Mon, Dec 19, 2011 at 18:14, Pavel Stehule wrote:
>> you can disable check per session if you need
>> ALTER TABLE ... DISABLE TRIGGER ALL;
>
> This is NOT a per-session command, this applies to all connections and
> queries, and may allow incorrect data into the tab
On Mon, Dec 19, 2011 at 18:14, Pavel Stehule wrote:
> you can disable check per session if you need
> ALTER TABLE ... DISABLE TRIGGER ALL;
This is NOT a per-session command, this applies to all connections and
queries, and may allow incorrect data into the table. Don't do this!
(And it doesn't ad
Hello
2011/12/19 Daniel Migowski :
> Hi,
>
>
>
> I face the following problem: I have a large table with 12 million
> addresses, referenced by 20 other tables (some containing about one million
> entries). There are indexes on the foreign keys.
>
>
>
> Now I wanted to delete about 10 million addre
On Tue, Dec 20, 2011 at 3:01 AM, Daniel Migowski wrote:
> DELETE FROM address
>
> WHERE id NOT IN (SELECT address_id FROM bank where address_id IS NOT NULL)
>
> AND id NOT IN (SELECT poboxaddress_id FROM bank where poboxaddress_id IS
> NOT NULL)
>
> AND id NOT IN (SELECT address_id FROM bank
Hi,
I face the following problem: I have a large table with 12 million addresses,
referenced by 20 other tables (some containing about one million entries).
There are indexes on the foreign keys.
Now I wanted to delete about 10 million addresses (that are not referenced
anymore from anywhere),
Until v. 9.1 enum modification was not officially supported, although hacking
pg_enum made it somewhat workable. Since v. 9.1 there is a way to add values to
enum types. However,
- alter type ... add value doesn't work in transaction blocks, which severely
limits its usefulness
- there is still
Don't worry ! I will surely try some different alternatives anyways, but the
idea is the same, include somehow a select for update in the same sentence
as the update. I'm most inclined to the last one you suggested, maybe with
an equals instead of an in (I'd rather always instinctively use an equal
On Thu, Sep 8, 2011 at 4:32 PM, Merlin Moncure wrote:
>> On Thu, Sep 8, 2011 at 1:22 PM, Merlin Moncure wrote:
>>>
>>> On Thu, Sep 8, 2011 at 4:01 AM, Eduardo Piombino
>>> wrote:
>>> > Hi, would it be possible to implement a nowait modifier to the update
>>> > statement in order to tell it not t
> On Thu, Sep 8, 2011 at 1:22 PM, Merlin Moncure wrote:
>>
>> On Thu, Sep 8, 2011 at 4:01 AM, Eduardo Piombino
>> wrote:
>> > Hi, would it be possible to implement a nowait modifier to the update
>> > statement in order to tell it not to wait and raise an error -just like
>> > a
>> > select for u
I'm sorry, isn't it meant for table locks?
I was talking about row level locking.
Eduardo
2011/9/8 pasman pasmański
> Try a command LOCK NOWAIT
>
> 2011/9/8, Eduardo Piombino :
> > Hi, would it be possible to implement a *nowait *modifier to the
> > *update*statement in order to tell it not to
Nice.
Much more maintainable IMO and quite close to what I was looking for.
Thanks a lot for the suggestion, I will definitely try it/implement it right
away.
Still has some redundancy compared to an hypothetical nowait modifier but I
think it's the very best alternative so far.
Eduardo
On Thu, S
Try a command LOCK NOWAIT
2011/9/8, Eduardo Piombino :
> Hi, would it be possible to implement a *nowait *modifier to the
> *update*statement in order to tell it not to wait and raise an error
> -just like a
> select for update nowait would-, instead of defaulting to waiting forever
> until the lo
On Thu, Sep 8, 2011 at 4:01 AM, Eduardo Piombino wrote:
> Hi, would it be possible to implement a nowait modifier to the update
> statement in order to tell it not to wait and raise an error -just like a
> select for update nowait would-, instead of defaulting to waiting forever
> until the lock b
On Thu, Sep 8, 2011 at 10:01 AM, Eduardo Piombino wrote:
> Hi, would it be possible to implement a nowait modifier to the update
> statement in order to tell it not to wait and raise an error -just like a
> select for update nowait would-, instead of defaulting to waiting forever
> until the lock
Hi, would it be possible to implement a *nowait *modifier to the
*update*statement in order to tell it not to wait and raise an error
-just like a
select for update nowait would-, instead of defaulting to waiting forever
until the lock becomes available?
The lack of such a modifier nowadays forces
Thanks, i'll try it tomorrow
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
pasman pasmañski writes:
> Hi.
>
> Is this possible to limit number of connections for given user/role?
> Postgres 8.4.8.
Yes. Read up on ...
create/alter role
alter role $role connection limit 10;
>
> pasman
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresq
Hi.
Is this possible to limit number of connections for given user/role?
Postgres 8.4.8.
--
pasman
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Merlin Moncure writes:
> On Wed, Aug 24, 2011 at 11:30 AM, Richard Broersma
>> The following email illustrates the behavior that is undesirable (to me).
>> http://www.mail-archive.com/pgadmin-support@postgresql.org/msg11482.html
> this is IMO not a feature, but a bug.
No, it's not a bug, it's ju
On Wed, Aug 24, 2011 at 10:14 AM, Merlin Moncure wrote:
> this is IMO not a feature, but a bug.
Would the feature I'm requesting be a bug or is it the current
behavior that would be considered a bug?
--
Regards,
Richard Broersma Jr.
--
Sent via pgsql-general mailing list (pgsql-general@post
On Wed, Aug 24, 2011 at 11:30 AM, Richard Broersma
wrote:
> It'd be nice if the catalog entries that store the DDL constraints
> definitions and view definitions with regular expressions strings
> would preserved any escape string syntax (i.e.E) for RegExp
> backslashes.
>
> For example, PGAdmin u
It'd be nice if the catalog entries that store the DDL constraints
definitions and view definitions with regular expressions strings
would preserved any escape string syntax (i.e.E) for RegExp
backslashes.
For example, PGAdmin uses these catalog entries to produce Create or
Replace scripts to that
On Fri, May 27, 2011 at 06:53:17AM +0200, A B wrote:
> hope) that by creating a view and select * from the view and send it
> over to the other server or use triggers to record what rows are
> inserted and deleted. (I have not written that part yet)
You could do this today with Slony or Londiste
On 27 May 2011 05:53, A B wrote:
> I have a small problem, in a database I need to export parts of a
> database table to another server, and I could easily accomplish ( I
> hope) that by creating a view and select * from the view and send it
> over to the other server or use triggers to record
Hi there!
I have a small problem, in a database I need to export parts of a
database table to another server, and I could easily accomplish ( I
hope) that by creating a view and select * from the view and send it
over to the other server or use triggers to record what rows are
inserted and delete
On 04/26/2011 04:33 PM, Tom Lane wrote:
luda posch writes:
I am not an expert on the official sql spec, but I think it would be useful
if distinct on() could be used within an aggregate when supplied with
another column name. For example:
select sum(distinct on(id) order_price) from order
luda posch writes:
> I am not an expert on the official sql spec, but I think it would be useful
> if distinct on() could be used within an aggregate when supplied with
> another column name. For example:
> select sum(distinct on(id) order_price) from order_table;
> select sum(distinct on(email_
I have used and it is quite useful the 'distinct' keyword within aggregate
functions.
I am not an expert on the official sql spec, but I think it would be useful
if distinct on() could be used within an aggregate when supplied with
another column name. For example:
select sum(distinct on(id) ord
Hallo,
i have a possible feature request.
It is not possible to get the sql statement itself and the output of the
statement in a user-friendly way to an output file (option \o psql),
this is only possible outside of psql, when calling this function with
an option -L (psql -L log.txt).
The nice t
hello.
I think that left/right joins and limit may be optimized.
When there aren't WHERE conditions this may be executed as below:
Limit N
Merge Left Join
Sort Top N
Bitmap Heap Scan
...
Sort
Bitmap Heap Scan
...
pasman
--
Sent via pgsql-general mailing li
Hi. Could you please consider logging size of reply, like Apache
httpd does with its logfile?
We've started having intermittent spikes in network usage (the network
interface on the
DB server is getting maxed out) and I suspect there is a single very
large query (just a
working hypothesis at this
On Tue, Nov 02, 2010 at 11:58:35AM -0400, zhong ming wu wrote:
> I looked on PG website but couldn't find admin email for this list
>
> I would like list emails to have extra 'reply-to' header addressed to the
> list
>
> Is it too much to ask? When replying from a mobile client it can be tricky
zhong ming wu writes:
> I would like list emails to have extra 'reply-to' header addressed to the
> list
> Is it too much to ask?
Yes. This is something that would break the messaging style that
everyone on these lists uses. Reply-to-all is the standard custom
around here.
I looked on PG website but couldn't find admin email for this list
I would like list emails to have extra 'reply-to' header addressed to the
list
Is it too much to ask? When replying from a mobile client it can be tricky
without + even from a bigger client most often I forgot
On Thu, Sep 23, 2010 at 16:20, Martin A. Brooks wrote:
> Hi
>
> I did not see this feature on the TODO page on the wiki. I apologise if I
> have overlooked something similar.
>
> I would like postgres to have a cron-like feature for scheduling things to
> happen at particular times.
>
> An exampl
Hi
I did not see this feature on the TODO page on the wiki. I apologise if I
have overlooked something similar.
I would like postgres to have a cron-like feature for scheduling things to
happen at particular times.
An example of this might be routinely purging data from tables, or
vacuuming spe
Greg Smith writes:
> Daniel Migowski wrote:
>> A small investigation showed to me that bzip2 compressed sql files
>> take only 60% of the space of gz compressed files. Since bzip2 is
>> fairly common today, could one add an option to pg_dump and pg_restore
>> supporting this compression type in
Daniel Migowski wrote:
A small investigation showed to me that bzip2 compressed sql files
take only 60% of the space of gz compressed files. Since bzip2 is
fairly common today, could one add an option to pg_dump and pg_restore
supporting this compression type in their custom format? Or do the
pg_dumpall | bzip2 > mydump.txt.bz2
bunzip2 -kc mydump.txt.bz2 | bin/psql template1
--
Scott Ribe
scott_r...@elevated-dev.com
http://www.elevated-dev.com/
(303) 722-0567 voice
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http:
Heyho!
On Friday 13 August 2010 10.57:13 Daniel Migowski wrote:
> A small investigation showed to me that bzip2 compressed sql files take
> only 60% of the space of gz compressed files.
But bzip2 is very slow. I think if there should be changes to the data
compression, xz is probably the futur
Hi, dear postgres developers,
A small investigation showed to me that bzip2 compressed sql files take
only 60% of the space of gz compressed files. Since bzip2 is fairly
common today, could one add an option to pg_dump and pg_restore
supporting this compression type in their custom format? Or
writes:
> , unique ( a_id , ( case when actual then 0 else id end ) )
> Why can i not define the unique constraint in the
> create table?
The syntax for a unique constraint in CREATE TABLE is defined by the SQL
standard, and it doesn't include expressions. More than the syntax, a
unique const
begin ;
create table a (
id serial primary key
, info text not null -- not interested here
) ;
create table b (
id serial primary key
, a_id int not null references a
, info text not null -- not interested here
, actual bool not null
) ;
create unique index b_actual on b
( a_id , (
On 1/28/09, Hermann Muster wrote:
> When creating a view via DBLINK, the user=... and password=... parameters
> shall be optional. If they are left out, then the current user accessing the
> view shall be impersonated implicitely to the "dblinked" database as well.
> Forcing anybody to hardcode a
When creating a view via DBLINK, the user=... and password=...
parameters shall be optional. If they are left out, then the current
user accessing the view shall be impersonated implicitely to the
"dblinked" database as well. Forcing anybody to hardcode a password
readable within the view defin
"Richard Broersma" <[EMAIL PROTECTED]> writes:
> UPDATE Foo
>SET ( a, b, c, ..., n ) = ( SELECT newA, newB, newC, ..., newN
> FROM Bar WHERE foo.id = Bar.id )
> Any thoughts on this?
It's been on the TODO list for quite some time:
http://wiki.postgresql
Regarding: row-wise update.
In a previous thread:
http://archives.postgresql.org/pgsql-sql/2008-08/msg00122.php
it was mentioned that the "UPDATE ... SET ... FROM ... WHERE" syntax
is an extension. (an extension employed by many other db flavors.)
This creates a problems since each db flavor is
Added to TODO:
o Add CREATE SCHEMA ... LIKE that copies a schema
---
[EMAIL PROTECTED] wrote:
> On Mar 17, 4:01 pm, wstrzalka <[EMAIL PROTECTED]> wrote:
> > Hi
> >
> >Features like CREATE DATABASE WITH TEMPLATE
On Sun, May 4, 2008 at 12:31 AM, Scott Marlowe <[EMAIL PROTECTED]>
wrote:
>
> You have the same type of problem if you have this query:
>
> select count(id), count(int2) from table.
>
> They both are named count. The simple answer is to always alias your
> select fields.
>
> select count(id) as i
On Fri, May 2, 2008 at 9:34 AM, Scott Miller <[EMAIL PROTECTED]> wrote:
> One problem I've had in development recently is the inability to get the
> aliased name of a table from a query. We're using a PHP framework for
> querying, which internally uses pg_field_name to retrieve the select list
> f
"Scott Miller" <[EMAIL PROTECTED]> writes:
> One problem I've had in development recently is the inability to get the
> aliased name of a table from a query. We're using a PHP framework for
> querying, which internally uses pg_field_name to retrieve the select list
> field name, which is great. T
One problem I've had in development recently is the inability to get the
aliased name of a table from a query. We're using a PHP framework for
querying, which internally uses pg_field_name to retrieve the select list
field name, which is great. There is alwo pg_table_name, to retrieve the
table t
On Mar 18, 2008, at 7:17 AM, Joris Dobbelsteen wrote:
Features like CREATE DATABASE WITH TEMPLATE or CREATE TABLE LIKE
are very usefull but it would be great to have such a feature on the
mid-level too. I mean something CREATE SCHEMA LIKE that would copy
all
the template schema relations, e
On Mar 17, 4:01 pm, wstrzalka <[EMAIL PROTECTED]> wrote:
> Hi
>
>Features like CREATE DATABASE WITH TEMPLATE or CREATE TABLE LIKE
> are very usefull but it would be great to have such a feature on the
> mid-level too. I mean something CREATE SCHEMA LIKE that would copy all
> the template schema
On Mon, Mar 17, 2008 at 9:01 PM, wstrzalka <[EMAIL PROTECTED]> wrote:
> Hi
>
>Features like CREATE DATABASE WITH TEMPLATE or CREATE TABLE LIKE
> are very usefull but it would be great to have such a feature on the
> mid-level too. I mean something CREATE SCHEMA LIKE that would copy all
> the
Joris Dobbelsteen wrote:
> wstrzalka wrote:
> > Hi
> >
> >Features like CREATE DATABASE WITH TEMPLATE or CREATE TABLE LIKE
> > are very usefull but it would be great to have such a feature on the
> > mid-level too. I mean something CREATE SCHEMA LIKE that would copy all
> > the template schema
wstrzalka wrote:
Hi
Features like CREATE DATABASE WITH TEMPLATE or CREATE TABLE LIKE
are very usefull but it would be great to have such a feature on the
mid-level too. I mean something CREATE SCHEMA LIKE that would copy all
the template schema relations, etc...
What do you think about it ?
Hi
Features like CREATE DATABASE WITH TEMPLATE or CREATE TABLE LIKE
are very usefull but it would be great to have such a feature on the
mid-level too. I mean something CREATE SCHEMA LIKE that would copy all
the template schema relations, etc...
What do you think about it ? Would it be hard to
1 - 100 of 167 matches
Mail list logo
