mito
mito copied to clipboard
An ORM for Common Lisp with migrations, relationships and PostgreSQL support
Hi, I have created 3 tables. users, courses and user-courses to implement a many-to-many relationship between the users and courses. When I try to access the user or courses object...
There may be a broken test with sqlite3. ``` Running a test file '/tmp/guix-build-sbcl-mito-0.1-1.d3b9e37.drv-0/source/t/migration/sqlite3.lisp' While evaluating the form starting at line 16, column 0 of #P"/tmp/guix-build-sbcl-mito-0.1-1.d3b9e37.drv-0/source/t/migration/sqlite3.lisp": Unhandled DBI.ERROR: in thread...
When trying to load mito using quicklisp I receive the following error: There is no applicable method for the generic function # when called with arguments (# :ALLOCATION-CLASS NIL). [Condition...
Any posibility to make something like this work? ``` cl (defclass category () ((parent :col-type category :initarg :parent :accessor parent)) (:metaclass mito:dao-table-class)) ```
I think it would be useful to support foreign key definitions for data integrity, You can always define your tables manually, but being able to do it whit mito would...
I'd like to count the number of rows a query returns. For example: ```lisp (mito:select-dao 'loan (sxql:where (:< :due-date (local-time:now)) (sxql:count) ;; ??? )) ``` `count-dao` accepts a model and...
Defining a class like so: ``` lisp (defclass tweet () ((user :col-type user :references user) (content :col-type :text)) (:metaclass mito:dao-table-class) (:unique-keys user)) ``` Causes a table definition with `(mito:table-definition 'tweet)`...
Does mito exposes a way to explicitly handle transactions? I have a use case in which I would like to update a object along with objects related to it, i.e....
Hi, Say I add a field to my model: ```lisp (due-date :col-type :timestamp :initform (local-time:timestamp+ (local-time:now) 60 :days) :accessor due-date) ``` When I run Mito's migrations, I get ``` Error...
The proposal is to add a column type like `(list :integer)` which will create a separate table to store list items. List items are all eagerly fetched. Also, handle types...