RE: EDS cry out!!!! Rob, Andy Sepa, anyone]
- Posted by Jonas Temple <jktemple at yhti.net> Apr 02, 2002
- 399 views
Jordah, I assume what you really want to do here is move key and data from one table to another. Here's a suggestion: I would create two sequences, maybe keys and data. I would also determine the largest amount of data you could store temporarily before you run out of memory. Then I would move a block (say 100 records) at a time from the source table to your keys and data sequences, switch to the target table and move the keys and data sequences to the target table. Then clear the keys and data sequences for the next block. You would, of course, need to retain the last record number you got from the source table so when you switched back to the source table you could pick up where you left off. Sorry, I don't have code examples, this is really just a theory. I think what you're frustrated over is the fact that you can only refer to one table in one database at a time. However, the intent of EDS was to be simple to use. That it is, but at the same time you sometimes have to be creative in how to accomplish what you're after. Jonas jordah ferguson wrote: > sorry rob, but i'm not getting you. > how would i copy these keys? coz the only way i know would be using > db_insert(). what do you mean they are unique. db_find_key returns an > integer eg1 or 3. isn't it possible it could interfere with other keys > in other tables. > > sorry, rob. i just don't know how the database.e library works? I know > how to use it and it is the key component of my application. please be a > > bit less technical. >