I have been experimenting with ClayDB and working on SQLite support. I managed to break Clay 2 today, but, like I said, "experimenting".
I'm trying to find that balance between ease of use and ease of development. The way it's looking right now, I may have to choose one. I think a lot of the readability issues can be solved by fixing some of the naming schemes in the database and standarding how data comes from the database. I don't want to weigh the code down, but I think a balance can be had by some standardization.
This particular change will make an upgrade from Clay 1 to Clay 2 very difficult, but not impossible. It involves quite a few changes to the database, but it does add a dimension of maintainability for the future.
Log in to comment