MySQL Forums
Forum List  »  Memory Storage Engine

Direct Access to Memory Tables
Posted by: Emiliano Marino
Date: September 21, 2005 12:16PM

Can I access Memory tables data using directly the memory engine functions (hp_open, etc) ?

I think that is posible, but I tried to run hp_test1.c but the program don't do that I suppose that it has to do (Its return errno=135/120 in every action that it's makes).

How can I run hp_test1.c correctly? What i'm doing wrong?

This is the output of running hp_test1.c :

- Creating heap-file
- Writing records:s
J= 25 heap_write: 135 my_errno: 135
J= 23 heap_write: 135 my_errno: 135
{...}
J= 4 heap_write: 135 my_errno: 135
J= 2 heap_write: 135 my_errno: 135
- Reopening file
- Removing records
key: 13 rkey: 120 my_errno: 120
{...}
key: 24 rkey: 120 my_errno: 120
- Reading records with key
key: 1 rkey: 120 my_errno: 120 record: 1 ..... key
key: 2 rkey: 120 my_errno: 120 record: 2 ..... key
{...}
key: 24 rkey: 120 my_errno: 120 record: 24 ..... key
key: 25 rkey: 120 my_errno: 120 record: 25 ..... key


We are developing a embedded system that uses Memory Tables to retain data that changes frequently in time. This data can be requested by some modules in the application using SQL statements. The problem is that some other modules must read and update data in the table very frequently and making this using individual UPDATE commands take too long (every time I want to update a simple value, the DB must parse the query, etc). I think that if I use the Memory Engine functions directly, can access to the tables skiping the parsing part.

thanks



Edited 1 time(s). Last edit at 09/21/2005 02:29PM by Emiliano Marino.

Options: ReplyQuote


Subject
Views
Written By
Posted
Direct Access to Memory Tables
7113
September 21, 2005 12:16PM
3790
September 22, 2005 01:57AM
3542
September 22, 2005 08:03AM
3868
September 23, 2005 04:36AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.