MiniMe
Posts: 210 Joined: Thu Mar 15, 2001 4:30 pm
Post
by MiniMe » Wed Nov 07, 2001 4:47 pm
Is there a way to build a table in memory during the invocation of a script, do all the processes to build a report and then the table dissapear at the end of the script.
Kai
Site Admin
Posts: 1272 Joined: Tue Apr 25, 2000 1:27 pm
Post
by Kai » Wed Nov 07, 2001 5:00 pm
<SQL "create ram table mytmptable(...)"></SQL>
Don't create any indexes on it though, as they will go to disk. See also <xtree> in Vortex for a fast in-RAM search structure.
MiniMe
Posts: 210 Joined: Thu Mar 15, 2001 4:30 pm
Post
by MiniMe » Wed Nov 07, 2001 5:10 pm
This is perfect.. thanks
MiniMe
Posts: 210 Joined: Thu Mar 15, 2001 4:30 pm
Post
by MiniMe » Wed Nov 07, 2001 5:13 pm
Is it possible to have <timport> populate the ram table??
John
Site Admin
Posts: 2623 Joined: Mon Apr 24, 2000 3:18 pm
Location: Cleveland, OH
Post
by John » Wed Nov 07, 2001 5:33 pm
Within Vortex <timport> puts the values into variables, that you can then insert into the table.
John Turnbull
Thunderstone Software
bart
Posts: 251 Joined: Wed Apr 26, 2000 12:42 am
Post
by bart » Sun Mar 07, 2010 9:57 am
I cant seem to find the doc pages describing ram table creation and dropping.
mark
Site Admin
Posts: 5519 Joined: Tue Apr 25, 2000 6:56 pm
Post
by mark » Mon Mar 08, 2010 9:52 am
Good point. It doesn't appear to be documented. It's basically the same though. Just add the "ram" keyword to the create. Nothing special about drop.
create ram table foo(id counter,Name varchar(20));
drop table foo;
Kai
Site Admin
Posts: 1272 Joined: Tue Apr 25, 2000 1:27 pm
Post
by Kai » Mon Mar 08, 2010 11:44 am
Keep in mind that the RAM table is currently tied to the <sql> handle and its derivatives, i.e. it may not always be visible to a later <sql> with different handle parentage, even for the same database and no <sqlcp cache close> (which would free any/all RAM tables).