Archive for the ‘SQL’ Category.

Is UniVerse non-relational?

This morning, I received an email summary of my linked-in activities. One of the network activities was Susan Joslyn comment that U2 had been added to the non-sqldatabases.org website.

Continue reading ‘Is UniVerse non-relational?’ »

More on UniVerse to MySQL

I have now been able to do simple sql statements from within UniVerse to access data in MySQL.

All good stuff.

As I really want to see how I can use MySQL as a multivalued database, I have decided to cheat a bit. MySQL 5.1 has some xml inbuilt functionality. It is possible to extract and update a value within a xml string stored in a MySQL field.

Continue reading ‘More on UniVerse to MySQL’ »

UniVerse odbc to MySQL

I wanted to see how easy it was to access a MySQL database from UniVerse; using UniVerse as the client.

This is on Linux (CentOS 4) with UniVerse 10.2 PE.

Continue reading ‘UniVerse odbc to MySQL’ »

Further Thoughts on MySQL Proxy

I have been thinking about how easy it would be to implement the previously mentioned idea of using MySQL Proxy as a uniVerse query processor/converter to SQL.

Now, the CREATE.FILE can be translated to a number of create table statements within SQL and DELETE.FILE to drop table respectively; and SORT to a select etc.

But, there is actually no equivalent to the SQL alter within uniVerse at the ECL or query level.

So, it becomes quite difficult to create and alter field definitions within a file.

This is actually a deficiency within the PICK/uniVerse world. Field definitions have always been done via some sort of user screen (REVISE) or editor (ED), not by a command line; either at file creation time (as in SQL) or otherwise. If the MySQL Proxy idea was to be developed, then this would have to be overcome via a new pseudo command.

It is still an interesting situation that PICK/uniVerse has never had a need (apparently) for an alter though…

MySQL Proxy – MySQLForge Wiki

The latest Linux Magazine (October 2007) has an article about MySQL Proxy – MySQLForge Wiki.

This is a piece of software that sits between the MySQL client (or any sql client) and MySQL server. It traps the SQL commands and via a small embedded programming language (LUA) the command can be modified on the fly.

The significance?

Continue reading ‘MySQL Proxy – MySQLForge Wiki’ »

DIY B-Tree’s

While reading through the PICK entry on the wikipedia.org website, I found a link to www.semaphorecorp.com which has code and instructions on writing your own b-tree’s within PICK.

It is dated from 1987…