UPSERT

This strange word is a composition of UPDATE and INSERT. It's a technique, when INSERT is not possible, mostly due to key conflicts, so UPDATE is performed instead.

ON DUPLICATE KEY UPDATE

The most common UPSERT is 

1. INSERT INTO table (column_names) VALUES (data) ON DUPLICATE KEY UPDATE column1 = expression, column2 = expression...;

asdf

INSERT IGNORE

asdf

1. INSERT IGNORE INTO table_name (column_names) VALUES ( value_list), ( value_list) .....;

asdf

REPLACE

asdf

1. REPLACE [INTO] table_name(column_list) VALUES(value_list);

asdf

Storage

While I’ve been writing less into this blog, I’ve been writing much more into the QetriX Wiki. Mostly because I need my thoughts sorted and make definitive statements about functionalities.

As usual, I ended up at storage and files, but this time, having much more experience in this field and one proved solution, it’s much easier to define it. It’s nice to see how stuff clicks together.

I even came with support for multiple DataStore at once! The only rule is there has to be a primary DataStore, where types and settings are stored. The other DataStores are as CC (like in e-mails), which receive the data from the primary DataStore.

Page Path Parts

QetriX Application consists of pages. If a page has path property, it's accessible via URL and should provide some kind of output.

Path also define other aspects of the page, like what app or site it belongs to. The Framework supports multiple apps running on the same core and domain, as well as multiple sites. Of course, apps and sites are optional.

“Site” is a standalone part of an App, like user space. For blogging service it would be individual blogs, where content and data is separated from other sites (blogs). The difference between App and Site is that Sites share the same resources, while Apps don't.

Multi-app multi-site path example: /blogs/qetrix/2016/04/page-path-parts. “Blogs” is an App, “qetrix” is a Site and the rest is a path of the page. App and Site names always corresponds to a directory structure on server's file system, Page path is often a database entry.