(60% complete; constructing)
- LIFEYM: comparison table
[LIGROU: ~"110MB" as of "February 2006" .]
LIFJGP: additional DB in XML vs. SQL Since we can start fresh, seems best to start with XML DB, the better choice (perhaps given time) if support for it continues to grow. Simulate XInclude & XQuery it in PHP suggests XML is #1 for inter-op, so useful to simulate it (as perhaps when one's not lucky enough to start w/ an XML DB?) Seemingly all SQL DBs output to XML for portability. XML much more expressive now & offers greater potential if properly supported. LIF83E: SQL DB as MySQL (beyond WordPress,) considering strongly not natural but well-supported medium: required structure powerful when it near-exactly fits but constraining when it doesn't or when partially fits. Typically requires programmer (formal schema edits) to extend (unless variable-field extensions used, which are possible but non-standard & not-well supported). Limited static types usually (unless say SQLite). Data NOT readily nest-able unless one builds nesting structures which then easily complicate code. Text, even XML, is not typically parsed & indexed in any way by default except for full-text search, unless XML support added. Ops take & return tables mostly. medium-high (as structure is constraining) to (medium due to regular exceptions). Exceptions: a field is dynamically typed in SQLite, not in other SQL. highest (including OLAP ). [LIGRTT: Query from SQL shows XQuery seems somewhat more expressive but that doesn't get into high-end SQL.] seems medium to high seems requires translation in most cases, esp. given stored-procedure syntax & needed extensions are not standard ? ? SQL Update, many interfaces, incl. MySQL Workbench ~100GB here(search for MySQL) suggested by here
LIP77I: Section Change Table (in order)
ID + Link(s) (Starting setting/environment), else attribute How modifying When: Planned Actual Starting Reason including inspiration & preparation Results Ender: Planned Actual LIGTPJ: draft source's section Backend-Technology options (for tables) added none in progress; ~80% usual done immediately none none LIGTSV: SV 0H publish draft today ; LIJG54: posting: 23 March, 2011 @ 18:33 Want to put "II'll arrive ~8pm. I now work full-time w/ WordPress (its own PHP framework w/ MySQL) &we're starting a move2 XML DB (XQuery) per http://1.JotHere.com/368#LIGUKH ,but it's good to keep abreast w/ other technologies as this & hang w/ fellow techies :-)" on LIF8D5 reference in comment on http://meetup.com/oc-php/events/16330189/ done immediately none none LIP79R: all see Svn r873 LIP64W: row 64W source's content (from same name in JotHere.com table) move to here none now-~1hr source was becoming big so way too slow to edit in MS ExWeb 4. none none LIP7R0: title exists not. set to "Backend-Technology options for tables” now right after row 64W research for JotHere, also shared tot he world, since I make a lot of tables. done immediately none none LIP7R6: post exists not. set to now right after row 64W usual done immediately none none LIP3KG: draft source exists not. set to 379[table_backend_tek]_LIP3KG.htm, copying via TortoiseSVN from 368[JotHere.com_table]_LIF505.htm as a template to start this file especially this table. now now since th content here I entirely moved from there. done immediately none none source's content (template row; copy & paste it then edit to suit) now usual done immediately none none
Copyright © 2011 by http://JotHere.com with all rights reserved.