Re: WO Equivalent of prepared statement
Re: WO Equivalent of prepared statement
- Subject: Re: WO Equivalent of prepared statement
- From: Guido Neitzer <email@hidden>
- Date: Mon, 27 Oct 2008 23:15:28 -0600
On 27.10.2008, at 21:02, Cheong Hee (Datasonic) wrote:
You need to map the data to the column name properly, generate
primay keys etc. I probably did it the wrong way,
and I need to generate my own primary key for each raw data to
insert into db.
It really depends on the database and it is not hard to use the same
mechanisms WebObjects uses. In PostgreSQL sequences, in FrontBase the
"select unique ..." feature and so on.
In EOF, the eo primary key table is created to primary keys. What
you need is much easier, as appreciate EOF more when I did the
prepared statement.
That is definitely true and I normally also try to do things with WO,
but when I had the requirements of importing around 300000 rows four
times every day in the shortest possible time, I still used the
PostgreSQL copy command, because it did the job in a couple of seconds
when the files where prepared properly while WO took more than 30
minutes ...
There are many situations where EOF is the right tool, but there are
also situations where there are better and faster ways.
Even with WebObjects you should recognize a screw even if you only
have a hammer at hand ...
cug
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden