-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
I am in the middle of moving a product from MySQL to Postgre. One of
the tables is relatively big, with 100M+ rows and growing, each of
which has a column that usually contains between 1-500k of data (the
'MYD' file it is currently 94G).
I have a clue to this problem, see below.
On 3/11/07, Geoff Russell <[EMAIL PROTECTED]> wrote:
Hi all,
I have postgresql 8.1, unixodbc and openoffice on a Ubuntu 6.06.1
machine and can connect to my postgresql
databases fine --- but can't edit data, only view. pgadmin3 also only
allows viewing
Hi everyone!!
I have an implementation of tsearch2 with spanish stemmers. I
updated
postgres to 8.1.8 version and I was going to reinstall the
tsearch2
contrib, everything was fine until I try to compile the spanish
stemmers
with gend
Rajarshi Guha <[EMAIL PROTECTED]> writes:
> ... I found this posting
> (http://www.thescripts.com/forum/thread399934.html) from 2005, which
> indicates that a pl/Python procedure will not see an array type as array
> but rather as a string.
> Has this aspect been updated?
AFAICS, plpython still d
Hi, I have a table in which a column is of type real[12]
I also have a function written in pl/Python that will accept two
arguments of type real[12].
However when I send in the values by doing:
select sim(ARRAY[1,1,1,1,1,1,1,1,1,1,1,1], ARRAY[1,1,1,1,1,1,1,1,1,1,1,1])
I get an error indicating
"Alain Roger" <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> i created the following function :
> -- Function: immense.sp_a_001(username "varchar", pwd "varchar")
> -- DROP FUNCTION immense.sp_a_001(username "varchar", pwd "varchar");
>
> CREATE OR REPLACE FUNCTION immense.sp_a_001(username "varchar", pw
On 11/03/07, Alain Roger <[EMAIL PROTECTED]> wrote:
Hi,
i created the following function :
-- Function: immense.sp_a_001(username "varchar", pwd "varchar")
-- DROP FUNCTION immense.sp_a_001(username "varchar", pwd "varchar");
CREATE OR REPLACE FUNCTION immense.sp_a_001(username "varchar", pwd
"
Hi,
i created the following function :
-- Function: immense.sp_a_001(username "varchar", pwd "varchar")
-- DROP FUNCTION immense.sp_a_001(username "varchar", pwd "varchar");
CREATE OR REPLACE FUNCTION immense.sp_a_001(username "varchar", pwd
"varchar")
RETURNS int4 AS
$BODY$
DECLARE
myrec imme
Community members of Nortern Europe:
I'll be in Oslo twice later this month, once on 3/17 and again for the Sun
Oslo Open Source Day:
http://no.sun.com/sunnews/events/2007/mar/opensource/agenda.html
If anybody lives in Olso, or can pop down for a quick 1/2 day, I'd really like
to meet you.
--
Martijn van Oosterhout writes:
> On Sun, Mar 11, 2007 at 11:09:56AM +0100, Christian Schr=F6der wrote:
>> Of course, if a NULL always means "unknown", then this approach doesn't
>> make sense. Where can I find an authorative definition of what NULL
>> means?
> Nowhere.
Well, in this context the
Reuven--
a few years back this same scenario happened for me working on a project with a
large Oracle DB which held clinical data
We needed to implement a join condition but the column we were using wa not
using an Index scan
so since the cardinality of the results was extraordinary we re-impl
Hi all,
I have postgresql 8.1, unixodbc and openoffice on a Ubuntu 6.06.1
machine and can connect to my postgresql
databases fine --- but can't edit data, only view. pgadmin3 also only
allows viewing
but not editing.
I can insert records with psql.
To make matters worse, I have another machine
On Sun, Mar 11, 2007 at 11:09:56AM +0100, Christian Schröder wrote:
> Of course, if a NULL always means "unknown", then this approach doesn't
> make sense. Where can I find an authorative definition of what NULL
> means? As I have quoted before, according to the Wikipedia (far from
> being authorat
Berend Tober wrote:
> Christian Schröder wrote:
>> Peter Eisentraut wrote:
>>
>>> A first step in that direction would be to rethink the apparently
>>> troublesome use of null values.
>> Some of the limits are
>> only valid after a given date, whereas other limits are valid all the
>> t
Christian Schröder wrote:
Berend Tober wrote:
Christian Schröder wrote:
Peter Eisentraut wrote:
A first step in that direction would be to rethink the apparently
troublesome use of null values.
Some of the limits are
only valid after a given date, whereas o
Used a different way but finally got my dependent views and table info for a
specific view. Here is how I did it:
==
declare
pos integer;
wh integer;
tot integer;
diff integer;
outp varchar;
viewn varchar;
begin
viewn := 'v2';
select position('FROM' i
16 matches
Mail list logo