>
> I'm using DBIx::Record set to great effect, but I've
> discovered a bug which annoys me. An SQL statement with joins
> in it doesn't need to name any tables, but if I leave out the
> !Tables parameter it produces a statement like 'SELECT *
> FROM', which the server rightly rejects with an
Hello,
I was just wondering what happens with Embperl pages that are stopped (stop
button) by the browser. Or when people first click one link and decide to click
something else before the pages finishes loading.
So far I have never had any problems but it micht be a cause of problems in the
futu
Two words: database transactions.
That said, I've found that apache usually finishes processing the
request but you're better off not assuming this and dealing with
transactional failure properly in your application.
--
Andrew O'Brien
Development Manager
e: [EMAIL PROTECTED]p: +61 2 9461 01
Gerald Richter wrote:
I'm using DBIx::Record set to great effect, but I've
discovered a bug which annoys me. An SQL statement with joins
in it doesn't need to name any tables, but if I leave out the
!Tables parameter it produces a statement like 'SELECT *
FROM', which the server rightly rejects
>
> What is it doing with the table names in this case?
It tries to figure out the metadata for the tables (like field types) to
make sure your parameter work correctly and (only in case you return fields)
checks if there are any links to other tables.
> Is it
> only working
> in this case be
