Re: updating a field speed improvement.

why not add a sequentially generated key as the primary? keeps your records unique that way.

desc your table's structure here.

why is calculating the weekending date a lengthy procedure? (syntax etc.)

describe in more detail what you are trying to accomplish/why, and the version of your db/os etc., if you have any limitations that you are working under, an approximate of the rows you are working with, the indexes/indexed columns etc.

then more specific help will come etc.

Craig Lehn wrote:
>
> Problem the problem I am in countering is..
> I have a table named "weekly" which contains a date for which hours were
> worked on, I need to include a column which has the week-ending date in it.
> i have no primary key and hence it requires the update be based on all the
> information currently available in the row.
>
> My current solution to this problem is to take the table afterwards and
> query the wdate(the date which the hours were placed against). Then after
> that calculate the weekending date, from there update the database with the
> entry. This is a fairly lengthy procedure.
>
> Is there something other then the cursor to allow assignment of the date
> row? Is there a way to figure out the date ending on the insert?(I doubt it)
> Is there a way to buffer all the data so there is one big insert at the end?
> Or is there any other options?
>
> Thanx ahead of time.
>
> -----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
> http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
> Check out our new Unlimited Server. No Download or Time Limits!
> -----== Over 80,000 Newsgroups - 19 Different Servers! ==-----
Received on Tue Feb 19 2002 - 12:01:21 CST