K
Kirk Haines
What Is Kansas?
===============
Kansas is a simple Object-Relational mapping layer for Ruby. It takes
a relational schema, accessible via Ruby's DBI layer, and converts it
in to a set of Ruby classes, one per table. Each class contains a set
of accessors corresponding to the columns in the table.
It is intended to be lightweight and easy to use to simplify interactions
with a relational database.
Kansas is currently ALPHA code. It's useable alpha code, and I don't
really expect the core features of the API to change significantly, but it
has some serious rough edges and missing pieces. Don't use it for
anything important, yet. That said, I would love it if anyone would
tinker with it a bit and give me some feedback.
It can be found on RubyForge:
http://rubyforge.org/projects/kansas
I also have the first draft of a portion of a tutorial on using Kansas
available:
http://enigo.com/projects/kansas
This is a living document. If you are looking at it tomorrow, it _will_
be wriggling around and growing a bit. I'd appreciate any comments anyone
might have on how to make it a better tutorial.
Thanks,
Kirk Haines
===============
Kansas is a simple Object-Relational mapping layer for Ruby. It takes
a relational schema, accessible via Ruby's DBI layer, and converts it
in to a set of Ruby classes, one per table. Each class contains a set
of accessors corresponding to the columns in the table.
It is intended to be lightweight and easy to use to simplify interactions
with a relational database.
Kansas is currently ALPHA code. It's useable alpha code, and I don't
really expect the core features of the API to change significantly, but it
has some serious rough edges and missing pieces. Don't use it for
anything important, yet. That said, I would love it if anyone would
tinker with it a bit and give me some feedback.
It can be found on RubyForge:
http://rubyforge.org/projects/kansas
I also have the first draft of a portion of a tutorial on using Kansas
available:
http://enigo.com/projects/kansas
This is a living document. If you are looking at it tomorrow, it _will_
be wriggling around and growing a bit. I'd appreciate any comments anyone
might have on how to make it a better tutorial.
Thanks,
Kirk Haines