On Friday 26 January 2007 00:40, Alan Gauld wrote:
> "Shadab Sayani" <[EMAIL PROTECTED]> wrote
>
> > I got your point.But before inserting data I need to store it
> > into a file in a format supported by postgresql.Wont this
> > operation incur a performance hit as it includes writing
> > to a fi
"Shadab Sayani" <[EMAIL PROTECTED]> wrote
>
> I got your point.But before inserting data I need to store it
> into a file in a format supported by postgresql.Wont this
> operation incur a performance hit as it includes writing
> to a file which is on disk?
Unless your data is already in a
"Eric Walstad" <[EMAIL PROTECTED]> wrote
>> Loadfile.sql would in turn contain lots of SQL commands like:
>>
>> INSERT into CUSTOMER
>> VALUES ( 'fred', 'bloggs', 45, '01773-987321');
> I think PostgreSQl will wrap each of these INSERT statements into a
> transaction, which will add a lot of over
Alan Gauld wrote:
> "Shadab Sayani" <[EMAIL PROTECTED]> wrote
>
>> Thank you very much for immediate response.I didnt get
>> the point of loading the data using SQL.What does that
>> mean?
>
> It means writing a SQL file that can then be run from
> the database SQL prompt. I don't know what tha
"Shadab Sayani" <[EMAIL PROTECTED]> wrote
> Thank you very much for immediate response.I didnt get
> the point of loading the data using SQL.What does that
> mean?
It means writing a SQL file that can then be run from
the database SQL prompt. I don't know what that means
in PostGres terms sinc
