Grant Gray wrote:
> #db.close   ##this throws out an error
> 
> This inserts key and value in the correct columns and does the correct
> amount of record entries.

So what exactly is your problem? That the above line throws an error? 
I'm afraid that if you don't show us either the actual error you get, 
nor a complete program which replicates the problem, then we can't help 
you.

If the problem is due to sqlite3 insert only, then it should be possible 
for you to boil this down to a simple test program which generates the 
same error, without using mysql. e.g.

my_data = [{"foo" => "bar", "baz" => "bap"}]
... now open a sqlite3 database, prepare, insert, close
... do you get the same error?

If you can do that, and post here an entire standalone program which 
demonstrates the problem, then (a) you may solve your problem in the 
process of boiling it down, and (b) if you don't, it will be much, much 
easier for someone else to help you, as they can just paste your program 
to replicate the problem.

As a separate point: you might find it easier to use an abstraction 
layer on top of mysql and sqlite3 so that you are using the same API to 
access both. ruby-dbi would give you a basic low-level compatibility for 
sending SQL. Sequel, Datamapper or ActiveRecord are higher-level 
alternatives, if you want to abstract away the SQL generation too.
-- 
Posted via http://www.ruby-forum.com/.