On Tue, 29 Nov 2005, Christian Neukirchen wrote:

> Hugh Sasse <hgs / dmu.ac.uk> writes:
> 
> > On Tue, 29 Nov 2005, Robert Klemme wrote:
> >
        [...]
> >> In fact it's likely that careful optimization on the database side will
> >> yield better results.  This can be as easy as creating some indexes - but
        [...]
> > At the moment my script to populate the tables is taking about an
> > hour.  Anyway it's mostly ruby I think, because it spends most of
> > the time setting up the arrays before it populates the db with them.
> 
> Do you use transactions correctly?

I've only got one process accessing the db at the moment.  If you've
got pointers on common errors, misconceptions, etc I'd be glad to
learn about them.   So I suppose that answer is likely to be "no"
:-)
> 
> > Besides that, I'm fairly new to database work, so I'm trying to
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > optimize what I know about before I start fiddling with the db.
> >

        Thank you,
        Hugh