Nana Sakisaka
Nana Sakisaka
I thought not to derive from `query` (sorry for my bad English), I meant something like this: ```cpp template class basic_query { public: typedef Self self_type; template self_type& where(COND const&...
And for dereferencing relations in lazy loading you can google "N+1 problem" - the library should have an eager-loading feature to avoid it. It's quite easy though - just publish...
- tag - attachment (which could be a nice example for introducing blobs)
As for many-to-many relationships Rails offers two methods `has_many :through` and `:has_and_belongs_to_many` where the latter is the shorthand form which could be written in single line. The former is a...
This page might give you a hint: http://guides.rubyonrails.org/association_basics.html#choosing-between-has-many-through-and-has-and-belongs-to-many
And the column `is_primary_category BOOLEAN` is the **custom attribute for the joining table** I mentioned. We really need it in some locations. As for many-to-many relationships there will be two...
Btw **Choosing between `VARCHAR(255)` and `VARCHAR(256)`** VARCHAR allocates extra bytes to determine the data length. - `VARCHAR(255)` = 255 bytes + **1 byte** = 256 bytes - `VARCHAR(256)` = 256...
> one_to_one isn't explicitly supported, you can achieve it with having a has_one attribute within each entity. But its not exactly what one_to_one stands for. I'm afraid that `has_one` +...
Refs issue #72
The problem for that method is that the user-defined types might be designed to use a (multiple) free function or something. And the most important issue is that you are...