Hi again
Just got to work again.
Thank you all for your answers! And I can see your point in "This is not a
DBI question". This problem was actually caused by wrong indexes in the
database.
Anyway- I think this it's nice when this mailing list can link to other
areas where the problems can be found. Working with the DBI interface
includes a lot of techniques and sometimes it's difficult to locate the
problem.
I always use this mailing list, cause I think that I always get serious
answers and I think that the people using this list runs into the same
troubles that I do. This is also a very active mailing list, which I havn't
been able to find elsewhere.
So, my point is actually - I think this list always will recieve "not a DBI
question", since you always get a hint of where to start troubleshooting
and I think that is a major access.
Once again - thank you all
/Michelle
"Wilson, Doug" wrote:
> This is not a DBI question.
>
> There's no reason that DBI would take any more
> time than the same query in SQL*Plus. Try the query there, get
> a query execution plan, see if you have missing indexes, need to
> create indexes, etc.
>
> -----Original Message-----
> From: Michelle Gerfort [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, June 12, 2001 6:17 AM
> To: [EMAIL PROTECTED]
> Subject: Slow execution
>
> Hi there
>
> I use an ordinary
> $sth->execute();
> but it seems to take ages to search, creating or updating a post.
> Is this problem due to the sqlstatement or is it a known problem with a
> perl DBI interface?
>
> I run Oracle 7.3.3 on an AIX 4.2 with roxen as webserver.
--
MVH
Michelle
-----------------------------------
Michelle Gerfort
Software Engineer
Teligent AB
P.O. Box 1191
SE-581 11 Link�ping, Sweden
www.teligent.se
