> >The system that I'm developing, I have about 25000 (persons) x 8
>>(exams)
>> x 15 (answers per exam) = 300 records to process and it is VERY SLOW.
>
>f you need to import large quantities of data, look at the copy
>command, that tends to be faster.
By way of example for the level of
"Josh Berkus" <[EMAIL PROTECTED]> writes:
> I just upgraded to 7.1 RC2. Two of my functions in the current
> development database used a variable called "row_count", which had no
> problems in 7.1 beta 3. They now bomb when called from PHP4, but not
> when run from PSQL. Huh?
row_count is a ke
Tom, Stephan, Bruce, All:
I just upgraded to 7.1 RC2. Two of my functions in the current
development database used a variable called "row_count", which had no
problems in 7.1 beta 3. They now bomb when called from PHP4, but not
when run from PSQL. Huh?
Changing the variable names fixed the pr
When I dump out my whole db with pg_dump -x dbname > dbname.out
then when I reload them, one of creation always failed
msg is relation 'urlinfo' is not exist,
so I dump out scheme first -- pg_dump -x -a dbname > dbname.out.s
reload them , samething happend, so I cut & paste the definition of
this
[EMAIL PROTECTED] writes:
> select *,
> (select a_typ from auftrag where a_nr=z_a_nr) as typ,
> (select a_t_definition_d from auftrags_typ where a_t_code=typ) as text
> from zylinder
Seems like a very non-SQLish way to proceed. Instead use joins:
select zylinder.*, a_typ as typ, a_t_definition_
[EMAIL PROTECTED] writes:
> Hello there
>
> I have another SQL question. Please see the example :
>
> select *,
> (select a_typ from auftrag where a_nr=z_a_nr) as typ,
> (select a_t_definition_d from auftrags_typ where a_t_code=typ) as text
> from zylinder
select zylinder.*,
auftrag.a_typ
(s
Hello there
I have another SQL question. Please see the example :
select *,
(select a_typ from auftrag where a_nr=z_a_nr) as typ,
(select a_t_definition_d from auftrags_typ where a_t_code=typ) as text
from zylinder
I have three tables that I need data from. I'd like to use the to
temporary sto
From: "Keith Gray" <[EMAIL PROTECTED]>
> Richard Huxton wrote:
> >
> > Indexes on underlying tables should be used though. Difficult to suggest
> > what indices you might need without knowing the view/tables/queries
> > involved.
>
> As an example I may have an "Invoice" table with several thousa
Yes but the option NOWAIT say to the instruction
SELECT ... FOR UPDATE to not wait the unlock but to return the information
the lines can't be lock.
(Must retry late).
Peter Eisentraut wrote:
[EMAIL PROTECTED]">Loïc Bourgeois writes:
What is the equivalent of the oracle request: SELECT ... FOR
