^LIF7T1:  =Backend-Technology options for tables

(60% complete; constructing) 

1. ^LIFEYM:  comparison table
   

   	LIF80C:	LIFF0J:	LIFXDV:	LIFJJF:	LIFSR7:	LIGRWX:	LIF89D:	LIGQSB:	LIGQQT:	LIF8SF:	LIF81R:	LIF8SP:	LIF85A: LIF85A	LIF8XS:	LIF8XK:  LIF8XK
   ID + Link(s)	description
   LIF8W3:	col header1	use on	use on	synergy with	data	data	code	code	code	display	display	edit	edit	edit	edit
   LIF801:	col header2	1.JotHere.com	notable sites		expressiveness	portability	capabilities	cleanliness	portability	in full	in full	in full	in full	snippet	snippet
   LIF8UU:	col header3	2011.03.21		HTML						tools	max size	tools	max size	tools	max size
   LIF80J: XHTML table-tag or similar CSS	XHTML table-tag, or similar CSS	heavy		identical	high; dynamic nest-able types & somewhat extensible.	medium for computation (revert to XML), high for viewing IF in the format one needs	LIJB08:  minimal or 0			web browser	100s of rows, .4MB example	MS Expression Web	LIJAXT:  ~100 rows * ~15 columns	none?
   LIFF3E:	Google Docs Spreadsheet	considering		"just" display live in iFrame			medium (JavaScript)			web browser		web browser
   LIF82T:	spreadsheet as .odt	only in background, as 6AE		export to XHTML but not well-supported			medium			OO Calc	same as editing	OO Calc	LIJC03:  ~1000 rows of say 15 columns, as 6AE
   LIF8D5: LIF8D5	XML DB as eXist or MarkLogic	LIGUKH: =LIGUKH: starting to try to move to it, likely on 2.JotHere.com	"O'Reilly Media uses MarkLogic Server to power its ground-breaking SafariU custom publishing application." said 2007.04 (2,3); I also recall hearing Safari Books Online (as a whole) heard this by an XQuery presenter at a 2007.01 SoCalCodeCampp; other MarkLogic users & here.	top (XHTML is  a subset); XRX is also notable, esp w/ GS[XSLTForms] and  XQIB (fr here)	Among highest available. Fully dynamic, nest-able, & extensible types, all which most. Some troublesome arbitrariness as (store as an attribute value or a tag value).	highest. The leading format	high; [LIGRQJ:  GS[XML DB spatial] finds some as in eXist; MarkLogic offers.] [LIGRRV: pivoting appears ~as easy as could be, easier than SQL, so easy it's not worth mention; but GS[XForms pivot table] found none.] [LIGRS8: Cached- & lazy-computation of queries? GS[cached views XML] shows academic work on that; still probable given NN]	seems very high (using leader  XQuery). (nest-able?) ops take & return core powerful data-type (XML).	seems high/ immediate			oXygen XML editors		XQuery, may interfaces	[LIGRNN: =NN:  MarkLogic std up to 40GB & ~"100s TB via cloud"] [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

   ^LIF7TN:  As an example reading this table, from it one can see tables < ~100 rows * ~15 columns which require minimal or 0 calculations can be done as an XHTML table-tag or similar CSS.

2. ^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 http://2.loverules.info/379	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