On 03/10/14 10:23, Michael Paquier wrote:
On Fri, Oct 3, 2014 at 4:57 PM, Albe Laurenz mailto:laurenz.a...@wien.gv.at>> wrote:
> Cedric Berger wrote:
>>>> 1) What is the easiest way to get that directly in C?
>>>
>>> The usual locution is "get_d
On 02/10/14 18:13, Tom Lane wrote:
Cedric Berger writes:
1) What is the easiest way to get that directly in C?
The usual locution is "get_database_name(MyDatabaseId)".
Ok, but then how do I find "MyDatabaseId" in, say,
a BeginForeignScan() or GetForeignRelSize()
installation/update scripts (like the @/extschema/@ substitution)?
Thanks,
--
Cedric Berger
Precidata Sarl
Maladière 71c
2000 Neuchâtel
ced...@precidata.com
032 930 29 62
079 934 11 02
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http:
installation/update scripts (like the @/extschema/@ substitution)?
Thanks,
Cedric
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Ivan Sergio Borgonovo wrote:
> On Thu, 06 Dec 2007 13:38:31 +0100
> Cedric Boudin <[EMAIL PROTECTED]> wrote:
>
>
>> It was indeed a forest problem.
>> both:
>>
>> set bolean_column= not bolean_column
>> and
>> set bolean_column= case w
Cedric Boudin wrote:
> Most honourable members of the list,
>
> this is a simple one, but I can't find the solution ( probably a
> forest/tree problem).
>
> update table set bolean_column = set_it_to_its_inverse where fk =
> some_value;
>
> or join
Most honourable members of the list,
this is a simple one, but I can't find the solution ( probably a
forest/tree problem).
update table set bolean_column = set_it_to_its_inverse where fk =
some_value;
or join me in the dark forest
cedric
---(end of broa
-If not, is it a bug?
have a nice day
cedric
**
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
Le samedi 10 mars 2007 06:32, Oleg Bartunov a écrit :
> On Fri, 9 Mar 2007, Jean-Michel Pour? wrote:
> > Le vendredi 09 mars 2007 ЪЪ 10:58 +0100, Magnus Hagander a ЪЪcrit :
> >> No idea. Assuming you want to do it beforehand. otherwise, just create
> >> the index and see how large it got?
> >
> > T
Le mardi 27 février 2007 15:00, George Nychis a écrit :
> Hey all,
>
> So I have a master table called "flows" and 400 partitions in the format
> "flow_*" where * is equal to some epoch.
>
> Each partition contains ~700,000 rows and has a check such that 1 field is
> equal to a value:
> "flows_
Le vendredi 23 février 2007 16:37, Ian Harding a écrit :
> On 2/22/07, Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> > Joshua D. Drake escribió:
> > > Andrej Ricnik-Bay wrote:
> > > > On 2/23/07, Jim Nasby <[EMAIL PROTECTED]> wrote:
> > > >> That depends greatly on what you're doing with it. Generall
Le mercredi 21 février 2007 15:44, Tom Lane a écrit :
> Markus Schiltknecht <[EMAIL PROTECTED]> writes:
> > Henrik Zagerholm wrote:
> >> Is this normal? What can I tweak in postgresql.conf to speed up big
> >> to_tsvector()?
> >
> > Hm.. seems not too unreasonable to me.
> > Take a look at the stem
Le mardi 30 janvier 2007 12:19, woger151 a écrit :
> (3) Use LASTVAL
for this one : look at
http://people.planetpostgresql.org/xzilla/index.php?/archives/169-Is-lastval-evil.html
>
> My questions:
> * Are any of these methods flawed?
> * Is there any reason to prefer (1) to (2)?
> * I'm not sure w
hi,
I'm facing this problem
DROP TABLE test;
DROP TABLE new_test;
CREATE TABLE test (id serial NOT NULL UNIQUE, nom varchar(32));
INSERT INTO test ("nom") values ('cedric');
INSERT INTO test ("nom") values ('felix');
INSERT INTO test ("nom"
hi,
let me explain what I have done, and what I'd like to do with a small example:
create table test (id serial, nom varchar(32));
INSERT INTO test ("nom") values ('cedric');
INSERT INTO test ("nom") values ('felix');
INSERT INTO test ("nom"
Synopsis
CREATE [ [ LOCAL ] { TEMPORARY | TEMP } ] TABLE /table_name/ (
{ /column_name/ /data_type/ [ DEFAULT /default_expr/ ] [ /column_constraint/ [, ...
] ]
| /table_constraint/ } [, ... ]
)
[ INHERITS ( /parent_table/ [, ... ] ) ]
[ WITH OIDS | WITHOUT OIDS ]
..
..
so this will mean
e varchar(32) CONSTRAINT nn__person__lastname NOT NULL
, email varchar(64) CONSTRAINT u__person__email UNIQUE
, phone varchar(32) CONSTRAINT u__person__phone UNIQUE);
Am'I interpreting wrongly the documentation or ... am
Hi,
how can we do this ?
CREATE TABLE test (key1 int, key2 int , primary key (key1,key2), parent
constraint parent references test );
Cédric BRINER
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archi
18 matches
Mail list logo
