https://wiki.kemiko.us/api.php?action=feedcontributions&feedformat=atom&user=Kemikokemiko - User contributions [en]2026-05-13T18:36:52ZUser contributionsMediaWiki 1.27.1https://wiki.kemiko.us/index.php?title=Main_Page&diff=429Main Page2024-12-14T18:35:19Z<p>Kemiko: </p>
<hr />
<div><table><br />
<tr><br />
<td><br />
[[File:120panes.png]]<br />
[http://www.panes.us &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;panes.us]<br />
</td><br />
<td><br />
[[File:120tux.png]]<br />
[http://tuxtummy.kemiko.us &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Tux Tummy]<br />
</td><br />
<td><br />
[[File:120calendar.png]]<br />
[http://calendars.kemiko.us &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Calendars]<br />
</td><br />
<td><br />
[[File:120menu.png]]<br />
[http://lunch.picksare.us &nbsp;&nbsp;&nbsp;Lunch Picks]<br />
</td><br />
<td><br />
[[File:120blank.png]]<br />
&nbsp;<br />
</td><br />
</tr><br />
</table><br />
<table><br />
<tr><br />
<td><br />
[[File:120camera.png]]<br />
[http://kohlmeyer.us &nbsp;&nbsp;&nbsp;Vacation Pix]<br />
</td><br />
<td><br />
[[File:120reversi.png]]<br />
[http://reversi.kemiko.us &nbsp;&nbsp;Open Reversi]<br />
</td><br />
<td><br />
[[File:120resume.png]]<br />
[http://resume.kemiko.us &nbsp;&nbsp;Kent's Resume]<br />
</td><br />
<td><br />
[[File:120invest.png]]<br />
[http://investments.picksare.us &nbsp;&nbsp;&nbsp;&nbsp;Investments]<br />
</td><br />
<td><br />
[[File:120blank.png]]<br />
&nbsp;<br />
</td><br />
</tr><br />
</table><br />
<br />
[http://wiki.kemiko.us/index.php/Home Home]<br />
<br />
[http://wiki.kemiko.us/index.php/Play Play]<br />
<br />
[[Work]]<br />
<br />
[[Misc]]<br />
<br />
[[Personal]]<br />
<br />
[[Computer]]<br />
<br />
[[Political]]<br />
<br />
[[Globe]]<br />
<br />
[[Clocks]]<br />
<br />
[[PDX]]<br />
<br />
[https://en.wikipedia.org/wiki/Excavator Excavator]<br />
<br />
[[Cargo Containers]]<br />
----<br />
<br />
[//wiki.kemiko.us/index.php/MediaWikiInstalled MediaWiki Installed]</div>Kemikohttps://wiki.kemiko.us/index.php?title=Clocks&diff=428Clocks2024-06-15T18:10:05Z<p>Kemiko: Added links.</p>
<hr />
<div>Everyone uses clocks daily. Some have more than just function...they are cool and of many styles.<br />
<br />
* [http://www.newworldencyclopedia.org/entry/Clock Clock]<br />
* [https://en.wikipedia.org/wiki/Clock Clock (WikipediA)]<br />
<br />
My favorite type of clocks are:<br />
* [https://en.wikipedia.org/wiki/Nixie_tube Nixie tube]<br />
* [https://en.wikipedia.org/wiki/Flip_clock Flip clock]<br />
* [https://en.wikipedia.org/wiki/Seven-segment_display Seven-segment display] (SSD)<br />
* [https://en.wikipedia.org/wiki/Clock#Analog Analog]<br />
* [https://en.wikipedia.org/wiki/Smartwatch Smartwatch]</div>Kemikohttps://wiki.kemiko.us/index.php?title=Main_Page&diff=427Main Page2021-09-06T19:27:19Z<p>Kemiko: </p>
<hr />
<div><table><br />
<tr><br />
<td><br />
[[File:120panes.png]]<br />
[http://www.panes.us &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;panes.us]<br />
</td><br />
<td><br />
[[File:120tux.png]]<br />
[http://tuxtummy.kemiko.us &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Tux Tummy]<br />
</td><br />
<td><br />
[[File:120calendar.png]]<br />
[http://calendars.kemiko.us &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Calendars]<br />
</td><br />
<td><br />
[[File:120menu.png]]<br />
[http://lunch.picksare.us &nbsp;&nbsp;&nbsp;Lunch Picks]<br />
</td><br />
<td><br />
[[File:120blank.png]]<br />
&nbsp;<br />
</td><br />
</tr><br />
</table><br />
<table><br />
<tr><br />
<td><br />
[[File:120camera.png]]<br />
[http://kohlmeyer.us &nbsp;&nbsp;&nbsp;Vacation Pix]<br />
</td><br />
<td><br />
[[File:120reversi.png]]<br />
[http://reversi.kemiko.us &nbsp;&nbsp;Open Reversi]<br />
</td><br />
<td><br />
[[File:120resume.png]]<br />
[http://resume.kemiko.us &nbsp;&nbsp;Kent's Resume]<br />
</td><br />
<td><br />
[[File:120invest.png]]<br />
[http://investment.picksare.us &nbsp;&nbsp;&nbsp;&nbsp;Investment]<br />
</td><br />
<td><br />
[[File:120blank.png]]<br />
&nbsp;<br />
</td><br />
</tr><br />
</table><br />
<br />
[http://wiki.kemiko.us/index.php/Home Home]<br />
<br />
[http://wiki.kemiko.us/index.php/Play Play]<br />
<br />
[[Work]]<br />
<br />
[[Misc]]<br />
<br />
[[Personal]]<br />
<br />
[[Computer]]<br />
<br />
[[Political]]<br />
<br />
[[Globe]]<br />
<br />
[[Clocks]]<br />
<br />
[[PDX]]<br />
<br />
[https://en.wikipedia.org/wiki/Excavator Excavator]<br />
<br />
[[Cargo Containers]]<br />
----<br />
<br />
[//wiki.kemiko.us/index.php/MediaWikiInstalled MediaWiki Installed]</div>Kemikohttps://wiki.kemiko.us/index.php?title=Main_Page&diff=426Main Page2021-09-06T19:21:23Z<p>Kemiko: </p>
<hr />
<div><table><br />
<tr><br />
<td><br />
[[File:120panes.png]]<br />
[http://www.panes.us &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;panes.us]<br />
</td><br />
<td><br />
[[File:120tux.png]]<br />
[http://tuxtummy.kemiko.us &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Tux Tummy]<br />
</td><br />
<td><br />
[[File:120calendar.png]]<br />
[http://calendars.kemiko.us &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Calendars]<br />
</td><br />
<td><br />
[[File:120menu.png]]<br />
[http://lunch.picksare.us &nbsp;&nbsp;&nbsp;Lunch Picks]<br />
</td><br />
</tr><br />
</table><br />
<table><br />
<tr><br />
<td><br />
[[File:120camera.png]]<br />
[http://kohlmeyer.us &nbsp;&nbsp;&nbsp;Vacation Pix]<br />
</td><br />
<td><br />
[[File:120reversi.png]]<br />
[http://reversi.kemiko.us &nbsp;&nbsp;Open Reversi]<br />
</td><br />
<td><br />
[[File:120resume.png]]<br />
[http://resume.kemiko.us &nbsp;&nbsp;Kent's Resume]<br />
</td><br />
<td><br />
[[File:120invest.png]]<br />
[http://investment.picksare.us &nbsp;&nbsp;&nbsp;&nbsp;Investment]<br />
</td><br />
<td><br />
[[File:120blank.png]]<br />
&nbsp;<br />
</td><br />
</tr><br />
</table><br />
<br />
[http://wiki.kemiko.us/index.php/Home Home]<br />
<br />
[http://wiki.kemiko.us/index.php/Play Play]<br />
<br />
[[Work]]<br />
<br />
[[Misc]]<br />
<br />
[[Personal]]<br />
<br />
[[Computer]]<br />
<br />
[[Political]]<br />
<br />
[[Globe]]<br />
<br />
[[Clocks]]<br />
<br />
[[PDX]]<br />
<br />
[https://en.wikipedia.org/wiki/Excavator Excavator]<br />
<br />
[[Cargo Containers]]<br />
----<br />
<br />
[//wiki.kemiko.us/index.php/MediaWikiInstalled MediaWiki Installed]</div>Kemikohttps://wiki.kemiko.us/index.php?title=File:120panes.png&diff=425File:120panes.png2021-09-06T19:18:33Z<p>Kemiko: Kemiko uploaded a new version of File:120panes.png</p>
<hr />
<div></div>Kemikohttps://wiki.kemiko.us/index.php?title=File:120panes.png&diff=424File:120panes.png2021-09-06T19:10:46Z<p>Kemiko: </p>
<hr />
<div></div>Kemikohttps://wiki.kemiko.us/index.php?title=Main_Page&diff=423Main Page2021-09-06T19:10:10Z<p>Kemiko: Added "Programs and Notes Execution System"</p>
<hr />
<div><table><br />
<tr><br />
<td><br />
[[File:120panes.png]]<br />
[http://www.panes.us &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Programs and Notes Execution System]<br />
</td><br />
<td><br />
[[File:120tux.png]]<br />
[http://tuxtummy.kemiko.us &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Tux Tummy]<br />
</td><br />
<td><br />
[[File:120calendar.png]]<br />
[http://calendars.kemiko.us &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Calendars]<br />
</td><br />
<td><br />
[[File:120menu.png]]<br />
[http://lunch.picksare.us &nbsp;&nbsp;&nbsp;Lunch Picks]<br />
</td><br />
</tr><br />
</table><br />
<table><br />
<tr><br />
<td><br />
[[File:120camera.png]]<br />
[http://kohlmeyer.us &nbsp;&nbsp;&nbsp;Vacation Pix]<br />
</td><br />
<td><br />
[[File:120reversi.png]]<br />
[http://reversi.kemiko.us &nbsp;&nbsp;Open Reversi]<br />
</td><br />
<td><br />
[[File:120resume.png]]<br />
[http://resume.kemiko.us &nbsp;&nbsp;Kent's Resume]<br />
</td><br />
<td><br />
[[File:120invest.png]]<br />
[http://investment.picksare.us &nbsp;&nbsp;&nbsp;&nbsp;Investment]<br />
</td><br />
<td><br />
[[File:120blank.png]]<br />
&nbsp;<br />
</td><br />
</tr><br />
</table><br />
<br />
[http://wiki.kemiko.us/index.php/Home Home]<br />
<br />
[http://wiki.kemiko.us/index.php/Play Play]<br />
<br />
[[Work]]<br />
<br />
[[Misc]]<br />
<br />
[[Personal]]<br />
<br />
[[Computer]]<br />
<br />
[[Political]]<br />
<br />
[[Globe]]<br />
<br />
[[Clocks]]<br />
<br />
[[PDX]]<br />
<br />
[https://en.wikipedia.org/wiki/Excavator Excavator]<br />
<br />
[[Cargo Containers]]<br />
----<br />
<br />
[//wiki.kemiko.us/index.php/MediaWikiInstalled MediaWiki Installed]</div>Kemikohttps://wiki.kemiko.us/index.php?title=Main_Page&diff=422Main Page2021-06-19T21:11:03Z<p>Kemiko: </p>
<hr />
<div><table><br />
<tr><br />
<td><br />
[[File:120tux.png]]<br />
[http://tuxtummy.kemiko.us &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Tux Tummy]<br />
</td><br />
<td><br />
[[File:120calendar.png]]<br />
[http://calendars.kemiko.us &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Calendars]<br />
</td><br />
<td><br />
[[File:120menu.png]]<br />
[http://lunch.picksare.us &nbsp;&nbsp;&nbsp;Lunch Picks]<br />
</td><br />
<td><br />
[[File:120camera.png]]<br />
[http://kohlmeyer.us &nbsp;&nbsp;&nbsp;Vacation Pix]<br />
</td><br />
</tr><br />
</table><br />
<table><br />
<tr><br />
<td><br />
[[File:120reversi.png]]<br />
[http://reversi.kemiko.us &nbsp;&nbsp;Open Reversi]<br />
</td><br />
<td><br />
[[File:120resume.png]]<br />
[http://resume.kemiko.us &nbsp;&nbsp;Kent's Resume]<br />
</td><br />
<td><br />
[[File:120invest.png]]<br />
[http://investment.picksare.us &nbsp;&nbsp;&nbsp;&nbsp;Investment]<br />
</td><br />
<td><br />
[[File:120blank.png]]<br />
&nbsp;<br />
</td><br />
</tr><br />
</table><br />
<br />
[http://wiki.kemiko.us/index.php/Home Home]<br />
<br />
[http://wiki.kemiko.us/index.php/Play Play]<br />
<br />
[[Work]]<br />
<br />
[[Misc]]<br />
<br />
[[Personal]]<br />
<br />
[[Computer]]<br />
<br />
[[Political]]<br />
<br />
[[Globe]]<br />
<br />
[[Clocks]]<br />
<br />
[[PDX]]<br />
<br />
[https://en.wikipedia.org/wiki/Excavator Excavator]<br />
<br />
[[Cargo Containers]]<br />
----<br />
<br />
[//wiki.kemiko.us/index.php/MediaWikiInstalled MediaWiki Installed]</div>Kemikohttps://wiki.kemiko.us/index.php?title=Informix&diff=421Informix2018-03-06T16:26:35Z<p>Kemiko: </p>
<hr />
<div>[https://en.wikipedia.org/wiki/IBM_Informix IBM Informix]<br />
<br />
This wiki article says, "Informix is generally considered to be optimized for environments with very low or no database administration, including use as an embedded database. It has a long track record of supporting very high transaction rates and providing uptime characteristics needed for mission critical applications such as manufacturing lines and reservation systems. Informix has been widely deployed in the retail sector, where the low administration overhead makes it useful for in-store deployments."<br />
<br />
<br />
I have worked with Informix in a very large reservation system, insurance and manufacturing. I find the above statement very true.<br />
<br />
<br />
I am currently working with <font color="red"><b>Informix 9.40.FC7</b></font> on HP-UX 11.11 as mostly an adminisrator not a developer. I recently added an <font color="red"><b>Informix 12.10.FC7WE</b></font> replicated server on RHEL 7.3. I started with <font color="red"><b>MySQL 3.23</b></font> on Linux and <font color="red"><b>Informix C-ISAM</b></font> on DEC Ultrix (pre IBM).<br />
<br />
*onstat commands are predefined queries that pull from the shared memory, sysmaster database, system files, etc.&nbsp;&nbsp;They are not output in the best format for reading or joining with other data...so use the sysmaster database to create your own reports with SQL joins&nbsp;&nbsp;([[Informix Monitoring]])<br />
*Learn the sysmaster database...this database holds configurations and statistics<br />
*ESQL/C is very fast for accessing the database. I used it to create session monitoring tool (itop) which is like *nix "top" or MySQL "mytop"<br />
*dbacces (output is vertical if width if greater than 80 characters) and isql are horrible SQL clients...use something like open source [http://squirrel-sql.sourceforge.net/ SQuirreL] for most queries. But, if you want to query table between Informix servers you have to use Informix tools like dbacces and isql.<br />
*Every database has catalog tables that hold table, column, index information, etc. (select tabname from systables where tabid < 100;)<br />
*Find columns with SQL...SELECT tabname, syscolumns.* FROM systables, syscolumns WHERE systables.tabid = syscolumns.tabid AND tabname = 'table'; or with ANSI join SELECT t.tabname, c.* FROM systables t JOIN syscolumns c ON t.tabid = c.tabid;<br />
*Raw devices are faster which Informix uses very well<br />
*Optimize your statistics plan for better performance<br />
*HPL (High Performance Loader) is a very awkward GUI tool, but can unload and reload tables quicker using a raw data format<br />
*Create enough space for logical logging to prevent downtime if the tape fails. The engine will block transaction if these logs can't be backed up<br />
*Large tables can really slow down OLTP databases. So, archive tables that are OLTP.<br />
*A "dummy" archive, ontape -s -L 0...w/TAPEDEV set to /dev/null (in onconfig), must be done after some configuration changes<br />
*Our Informix 9.40.FC7, which is 64 bit, has a 2GiB file limitation writing to HP-UX 11.11's file system...not the actual database data files going to a tape or pipe. So 9.40 can not archive a large database to disk without going to tape or through a pipe. 12.10 does not have this issue.<br />
*The system log only stamps the log with the date when the first record of the day is written...then only a time stamp is on the records.&nbsp;&nbsp;In 12.10 set "MSG_DATE 1" in the onconfig file to get the date stamp on each record.<br />
*Try and size your initial extents large enough that the engine does not have to keep creating more extents. Multiple extents fragment your table spaces.<br />
*Informix date and time fields/functions are very different from MySQL<br />
*I really like some of Informix's SQL extensions...like "||" for concatenation, field[n,m] for substring, field matches( regexp ), first, etc.<br />
*Don't hit ctrl-c while starting the database (command oninit)...this will leave share memory in limbo<br />
*Informix can do queries between 2 servers.&nbsp;&nbsp;Use lowercase strings for DBSERVERNAME and DBSERVERALIASES values<br />
*Do not OS "nice" dbaccess, etc. The engine handles the priority. Set MAX_PDQPRIORITY (Parallel Database Query) to process queries faster.<br />
*Informix is closely tied to the OS. Users and passwords are created and maintained by the OS.<br />
*Informix privileges are definitely different from MySQL. Informix has a "connect" grant that I like because it is the only privilges you need to revoke to deny a user access make other grants void! Also, Informix can list "all" grants in one statement...MySQL can not!<br />
*<font color="red">Informix 12.10 has a single user mode...does MySQL? (read_only=1)</font><br />
*Informix has had descending btree indexes since 9.40, but MySQL will not have them until 8.0.<br />
*Informix "CURRENT" operator vs MySQL NOW() function.<br />
*Informix &lt;database&gt;<font color="red"><b>:</b></font>&lt;table&gt;...MySQL &lt;database&gt;<font color="red"><b>.</b></font>&lt;table&gt;<br />
*Informix 9.40 did not have a "truncate" command!<br />
<br />
<br />
What are the differences between SQL statements with Informix and MySQL?&nbsp;&nbsp;(<font color="green">positive</font>/<font color="red">negative</font>/<font color="orange">neutral</font>)<br />
<table><br />
<tr><br />
<td><br />
Informix<br />
</td><br />
<td><br />
MySQL<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
<font color="orange"><b>database</b></font> database;<br />
</td><br />
<td><br />
<font color="orange"><b>use</b></font> database;<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
comments are: "<font color="orange"><b>{</b></font>" comment(s) "<font color="orange"><b>}</b></font>" or "<font color="orange"><b>--</b></font>"<br />
</td><br />
<td><br />
coments are: "<font color="orange"><b>/*</b></font>" comment(s) "<font color="orange"><b>*/</b></font>" or "<font color="orange"><b>--</b></font>"<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
<font color="red">A table NEEDS to be included in ALL select statements</font><br />
</td><br />
<td><br />
<font color="green">A table DOES NOT NEED to be included in select statements</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green"><b>MATCHES</b></font> <i><b>'regular_expr'</b></i> FROM <i><b>table</b></i>;<br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="red"><b>REGEXP</b></font> <i><b>'regular_expr'</b></i>;<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green"><b>||</b></font> <i><b>'select_expr'</b></i> FROM <i><b>table</b></i>;<br />
</td><br />
<td><br />
SELECT <font color="red">CONCAT(</font> <i><b>'select_expr'</b></i>, <i><b>'select_expr'</b></i> <font color="red">)</font>;<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <font color="red">FIRST i</font> <i><b>'select_expr'</b></i> FROM <i><b>table</b></i>;<br />
<font color="blue"><b>--OR</b></font><br />
SELECT <i><b>'select_expr'</b></i> FROM <i><b>table</b></i> <font color="green">LIMIT i</font>; {Informix version 12}<br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green">LIMIT i</font>;<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> FROM <font color="red"><i><b>table</b></i> WHERE 1 = 1</font>;<br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green">WHERE 1</font>;<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'<font color="green">[i,j]</font></b></i> FROM <i><b>table</b></i> 1 = 1;<br />
</td><br />
<td><br />
SELECT <font color="red">SUBSTR(</font> <i><b>'select_expr', <font color="red">i, j )</font> </b></i>WHERE 1;<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <font color="red">CURRENT</font> FROM <i><b>systables</b></i> WHERE <i><b>tabid = 1</b></i>;<br />
</td><br />
<td><br />
SELECT <font color="green">NOW( )</font>;<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT * FROM <i><b>database</b></i><font color="orange"><b>:</b></font><i><b>table</b></i>;<br />
</td><br />
<td><br />
SELECT * FROM <i><b>database</b></i><font color="orange"><b>.</b></font><i><b>table</b></i>;<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>database</b></i>:systables.tabname, <i><b>database</b></i>:syscolumns.*<br />
FROM <i><b>database</b></i>:systables<br />
JOIN <i><b>database</b></i>:syscolumns<br />
ON <i><b>database</b></i>:systables.tabid = <i><b>database</b></i>:syscolumns.tabid<br />
WHERE <i><b>database</b></i>:systables.tabname = '<i><b>table</b></i>';<br />
</td><br />
<td><br />
SELECT * <br />
FROM information_schema.columns<br />
WHERE table_schema = '<i><b>database</b></i>' AND table_name = '<i><b>table</b></i>';<br />
<font color="blue"><b>--OR</b></font><br />
<font color="green">DESCRIBE <i><b>database</b></i>.<i><b>table</b></i>;</font><br />
</td><br />
</tr><br />
</table><br />
<br />
<br />
[http://www.iiug.org/en/2017/07/29/compare-informix/ Compare the Informix Version 12 editions]<br />
<br />
<br />
<b>Informix NOTs</b><br />
<br />
-case sensitive<br />
<br />
-can't have spaces in AS</div>Kemikohttps://wiki.kemiko.us/index.php?title=Computers_101&diff=420Computers 1012017-12-02T22:13:29Z<p>Kemiko: </p>
<hr />
<div>* All computers are the same they use the same basic logic, storage etc.<br />
* Always make backups. Storage is cheap...so better to save too much than too little.<br />
* Many times the problem/solution is simple...don't over think it, but thought is good.<br />
* When accessing files/records without a sort (natural) they display as stored on disk. Usually by time at first, but becomes mixed as old files/records are deleted and new files/records are added.<br />
* Remember that everything is ones and zeros to a computer. So, letters and other data types are still just numbers.<br />
* Always do a select before a delete with everything...file system, database, application, etc.<br />
* When working with databases always rename objects before dropping...<br />
*Remember a little change can have large effects!<br />
*Always separate the OS from data on the hard drive.</div>Kemikohttps://wiki.kemiko.us/index.php?title=Database_101&diff=419Database 1012017-11-27T04:39:51Z<p>Kemiko: </p>
<hr />
<div>* Always do a "select" before a "delete"<br />
* Rename objects before deleting<br />
* Always use a "where" clause..."where 1" or "where 1 = 1" for all queryies or add a comment to make it clear that the query is selecting everything<br />
* Self joins can be handy<br />
* Use ANSI joins for clarity<br />
* Format SQL to for consistency and readability</div>Kemikohttps://wiki.kemiko.us/index.php?title=Main_Page&diff=418Main Page2017-11-21T02:50:22Z<p>Kemiko: </p>
<hr />
<div><table><br />
<tr><br />
<td><br />
[[File:120tux.png]]<br />
[http://tuxbytes.com &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Tux Bytes]<br />
</td><br />
<td><br />
[[File:120calendar.png]]<br />
[http://calendars.kemiko.us &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Calendars]<br />
</td><br />
<td><br />
[[File:120menu.png]]<br />
[http://lunch.picksare.us &nbsp;&nbsp;&nbsp;Lunch Picks]<br />
</td><br />
<td><br />
[[File:120camera.png]]<br />
[http://kohlmeyer.us &nbsp;&nbsp;&nbsp;Vacation Pix]<br />
</td><br />
</tr><br />
</table><br />
<table><br />
<tr><br />
<td><br />
[[File:120reversi.png]]<br />
[http://reversi.kemiko.us &nbsp;&nbsp;Open Reversi]<br />
</td><br />
<td><br />
[[File:120resume.png]]<br />
[http://resume.kemiko.us &nbsp;&nbsp;Kent's Resume]<br />
</td><br />
<td><br />
[[File:120invest.png]]<br />
[http://investment.picksare.us &nbsp;&nbsp;&nbsp;&nbsp;Investment]<br />
</td><br />
<td><br />
[[File:120blank.png]]<br />
&nbsp;<br />
</td><br />
</tr><br />
</table><br />
<br />
[http://wiki.kemiko.us/index.php/Home Home]<br />
<br />
[http://wiki.kemiko.us/index.php/Play Play]<br />
<br />
[[Work]]<br />
<br />
[[Misc]]<br />
<br />
[[Personal]]<br />
<br />
[[Computer]]<br />
<br />
[[Political]]<br />
<br />
[[Globe]]<br />
<br />
[[Clocks]]<br />
<br />
[[PDX]]<br />
<br />
[https://en.wikipedia.org/wiki/Excavator Excavator]<br />
<br />
[[Cargo Containers]]<br />
----<br />
<br />
[//wiki.kemiko.us/index.php/MediaWikiInstalled MediaWiki Installed]</div>Kemikohttps://wiki.kemiko.us/index.php?title=File:120blank.png&diff=417File:120blank.png2017-11-21T02:48:46Z<p>Kemiko: Kemiko uploaded a new version of File:120blank.png</p>
<hr />
<div></div>Kemikohttps://wiki.kemiko.us/index.php?title=Main_Page&diff=416Main Page2017-11-21T02:47:44Z<p>Kemiko: </p>
<hr />
<div><table><br />
<tr><br />
<td><br />
[[File:120tux.png]]<br />
[http://tuxbytes.com &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Tux Bytes]<br />
</td><br />
<td><br />
[[File:120calendar.png]]<br />
[http://calendars.kemiko.us &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Calendars]<br />
</td><br />
<td><br />
[[File:120menu.png]]<br />
[http://lunch.picksare.us &nbsp;&nbsp;&nbsp;Lunch Picks]<br />
</td><br />
<td><br />
[[File:120camera.png]]<br />
[http://kohlmeyer.us &nbsp;&nbsp;&nbsp;Vacation Pix]<br />
</td><br />
</tr><br />
</table><br />
<table><br />
<tr><br />
<td><br />
[[File:120reversi.png]]<br />
[http://reversi.kemiko.us &nbsp;&nbsp;Open Reversi]<br />
</td><br />
<td><br />
[[File:120resume.png]]<br />
[http://resume.kemiko.us &nbsp;&nbsp;Kent's Resume]<br />
</td><br />
<td><br />
[[File:120invest.png]]<br />
[http://investment.picksare.us &nbsp;&nbsp;&nbsp;&nbsp;Investment]<br />
</td><br />
<td><br />
[[File:120clear.png]]<br />
&nbsp;<br />
</td><br />
</tr><br />
</table><br />
<br />
[http://wiki.kemiko.us/index.php/Home Home]<br />
<br />
[http://wiki.kemiko.us/index.php/Play Play]<br />
<br />
[[Work]]<br />
<br />
[[Misc]]<br />
<br />
[[Personal]]<br />
<br />
[[Computer]]<br />
<br />
[[Political]]<br />
<br />
[[Globe]]<br />
<br />
[[Clocks]]<br />
<br />
[[PDX]]<br />
<br />
[https://en.wikipedia.org/wiki/Excavator Excavator]<br />
<br />
[[Cargo Containers]]<br />
----<br />
<br />
[//wiki.kemiko.us/index.php/MediaWikiInstalled MediaWiki Installed]</div>Kemikohttps://wiki.kemiko.us/index.php?title=Main_Page&diff=415Main Page2017-11-21T02:46:27Z<p>Kemiko: </p>
<hr />
<div><table><br />
<tr><br />
<td><br />
[[File:120tux.png]]<br />
[http://tuxbytes.com &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Tux Bytes]<br />
</td><br />
<td><br />
[[File:120calendar.png]]<br />
[http://calendars.kemiko.us &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Calendars]<br />
</td><br />
<td><br />
[[File:120menu.png]]<br />
[http://lunch.picksare.us &nbsp;&nbsp;&nbsp;Lunch Picks]<br />
</td><br />
<td><br />
[[File:120camera.png]]<br />
[http://kohlmeyer.us &nbsp;&nbsp;&nbsp;Vacation Pix]<br />
</td><br />
</tr><br />
</table><br />
<table><br />
<tr><br />
<td><br />
[[File:120reversi.png]]<br />
[http://reversi.kemiko.us &nbsp;&nbsp;Open Reversi]<br />
</td><br />
<td><br />
[[File:120resume.png]]<br />
[http://resume.kemiko.us &nbsp;&nbsp;Kent's Resume]<br />
</td><br />
<td><br />
[[File:120invest.png]]<br />
[http://investment.picksare.us &nbsp;&nbsp;&nbsp;&nbsp;Investment]<br />
</td><br />
<td><br />
[[File:120clear.png]]<br />
&nbsp;<br />
</td><br />
</tr><br />
</table><br />
<br />
<strong>Welcome to my wiki</strong><br />
<br />
[http://wiki.kemiko.us/index.php/Home Home]<br />
<br />
[http://wiki.kemiko.us/index.php/Play Play]<br />
<br />
[[Work]]<br />
<br />
[[Misc]]<br />
<br />
[[Personal]]<br />
<br />
[[Computer]]<br />
<br />
[[Political]]<br />
<br />
[[Globe]]<br />
<br />
[[Clocks]]<br />
<br />
[[PDX]]<br />
<br />
[https://en.wikipedia.org/wiki/Excavator Excavator]<br />
<br />
[[Cargo Containers]]<br />
----<br />
<br />
[//wiki.kemiko.us/index.php/MediaWikiInstalled MediaWiki Installed]</div>Kemikohttps://wiki.kemiko.us/index.php?title=File:120blank.png&diff=414File:120blank.png2017-11-21T02:45:43Z<p>Kemiko: </p>
<hr />
<div></div>Kemikohttps://wiki.kemiko.us/index.php?title=Main_Page&diff=413Main Page2017-11-21T02:45:27Z<p>Kemiko: </p>
<hr />
<div><table><br />
<tr><br />
<td><br />
[[File:120tux.png]]<br />
[http://tuxbytes.com &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Tux Bytes]<br />
</td><br />
<td><br />
[[File:120calendar.png]]<br />
[http://calendars.kemiko.us &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Calendars]<br />
</td><br />
<td><br />
[[File:120menu.png]]<br />
[http://lunch.picksare.us &nbsp;&nbsp;&nbsp;Lunch Picks]<br />
</td><br />
<td><br />
[[File:120camera.png]]<br />
[http://kohlmeyer.us &nbsp;&nbsp;&nbsp;Vacation Pix]<br />
</td><br />
</tr><br />
</table><br />
<table><br />
<tr><br />
<td><br />
[[File:120reversi.png]]<br />
[http://reversi.kemiko.us &nbsp;&nbsp;Open Reversi]<br />
</td><br />
<td><br />
[[File:120resume.png]]<br />
[http://resume.kemiko.us &nbsp;&nbsp;Kent's Resume]<br />
</td><br />
<td><br />
[[File:120invest.png]]<br />
[http://investment.picksare.us &nbsp;&nbsp;&nbsp;&nbsp;Investment]<br />
</td><br />
<td><br />
[[File:120blank.png]]<br />
&nbsp;<br />
</td><br />
</tr><br />
</table><br />
<br />
<strong>Welcome to my wiki</strong><br />
<br />
[http://wiki.kemiko.us/index.php/Home Home]<br />
<br />
[http://wiki.kemiko.us/index.php/Play Play]<br />
<br />
[[Work]]<br />
<br />
[[Misc]]<br />
<br />
[[Personal]]<br />
<br />
[[Computer]]<br />
<br />
[[Political]]<br />
<br />
[[Globe]]<br />
<br />
[[Clocks]]<br />
<br />
[[PDX]]<br />
<br />
[https://en.wikipedia.org/wiki/Excavator Excavator]<br />
<br />
[[Cargo Containers]]<br />
----<br />
<br />
[//wiki.kemiko.us/index.php/MediaWikiInstalled MediaWiki Installed]</div>Kemikohttps://wiki.kemiko.us/index.php?title=Main_Page&diff=412Main Page2017-11-19T00:27:59Z<p>Kemiko: </p>
<hr />
<div><table><br />
<tr><br />
<td><br />
[[File:120tux.png]]<br />
[http://tuxbytes.com &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Tux Bytes]<br />
</td><br />
<td><br />
[[File:120calendar.png]]<br />
[http://calendars.kemiko.us &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Calendars]<br />
</td><br />
<td><br />
[[File:120menu.png]]<br />
[http://lunch.picksare.us &nbsp;&nbsp;&nbsp;Lunch Picks]<br />
</td><br />
<td><br />
[[File:120camera.png]]<br />
[http://kohlmeyer.us &nbsp;&nbsp;&nbsp;Vacation Pix]<br />
</td><br />
<td><br />
[[File:120reversi.png]]<br />
[http://reversi.kemiko.us &nbsp;&nbsp;Open Reversi]<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
[[File:120resume.png]]<br />
[http://resume.kemiko.us &nbsp;&nbsp;Kent's Resume]<br />
</td><br />
<td><br />
[[File:120invest.png]]<br />
[http://investment.picksare.us &nbsp;&nbsp;&nbsp;&nbsp;Investment]<br />
</td><br />
</tr><br />
</table><br />
<br />
<strong>Welcome to my wiki</strong><br />
<br />
[http://wiki.kemiko.us/index.php/Home Home]<br />
<br />
[http://wiki.kemiko.us/index.php/Play Play]<br />
<br />
[[Work]]<br />
<br />
[[Misc]]<br />
<br />
[[Personal]]<br />
<br />
[[Computer]]<br />
<br />
[[Political]]<br />
<br />
[[Globe]]<br />
<br />
[[Clocks]]<br />
<br />
[[PDX]]<br />
<br />
[https://en.wikipedia.org/wiki/Excavator Excavator]<br />
<br />
[[Cargo Containers]]<br />
----<br />
<br />
[//wiki.kemiko.us/index.php/MediaWikiInstalled MediaWiki Installed]</div>Kemikohttps://wiki.kemiko.us/index.php?title=File:120invest.png&diff=411File:120invest.png2017-11-19T00:26:04Z<p>Kemiko: Kemiko uploaded a new version of File:120invest.png</p>
<hr />
<div></div>Kemikohttps://wiki.kemiko.us/index.php?title=File:120invest.png&diff=410File:120invest.png2017-11-19T00:21:35Z<p>Kemiko: Kemiko uploaded a new version of File:120invest.png</p>
<hr />
<div></div>Kemikohttps://wiki.kemiko.us/index.php?title=File:120invest.png&diff=409File:120invest.png2017-11-19T00:18:52Z<p>Kemiko: </p>
<hr />
<div></div>Kemikohttps://wiki.kemiko.us/index.php?title=Main_Page&diff=408Main Page2017-11-19T00:17:44Z<p>Kemiko: </p>
<hr />
<div><table><br />
<tr><br />
<td><br />
[[File:120tux.png]]<br />
[http://tuxbytes.com &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Tux Bytes]<br />
</td><br />
<td><br />
[[File:120calendar.png]]<br />
[http://calendars.kemiko.us &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Calendars]<br />
</td><br />
<td><br />
[[File:120menu.png]]<br />
[http://lunch.picksare.us &nbsp;&nbsp;&nbsp;Lunch Picks]<br />
</td><br />
<td><br />
[[File:120camera.png]]<br />
[http://kohlmeyer.us &nbsp;&nbsp;&nbsp;Vacation Pix]<br />
</td><br />
<td><br />
[[File:120reversi.png]]<br />
[http://reversi.kemiko.us &nbsp;&nbsp;Open Reversi]<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
[[File:120resume.png]]<br />
[http://resume.kemiko.us &nbsp;&nbsp;Kent's Resume]<br />
</td><br />
<td><br />
[[File:120invest.png]]<br />
[http://investment.picksare.us &nbsp;&nbsp;Investment]<br />
</td><br />
</tr><br />
</table><br />
<br />
<strong>Welcome to my wiki</strong><br />
<br />
[http://wiki.kemiko.us/index.php/Home Home]<br />
<br />
[http://wiki.kemiko.us/index.php/Play Play]<br />
<br />
[[Work]]<br />
<br />
[[Misc]]<br />
<br />
[[Personal]]<br />
<br />
[[Computer]]<br />
<br />
[[Political]]<br />
<br />
[[Globe]]<br />
<br />
[[Clocks]]<br />
<br />
[[PDX]]<br />
<br />
[https://en.wikipedia.org/wiki/Excavator Excavator]<br />
<br />
[[Cargo Containers]]<br />
----<br />
<br />
[//wiki.kemiko.us/index.php/MediaWikiInstalled MediaWiki Installed]</div>Kemikohttps://wiki.kemiko.us/index.php?title=Informix&diff=407Informix2017-10-27T21:39:29Z<p>Kemiko: </p>
<hr />
<div>[https://en.wikipedia.org/wiki/IBM_Informix IBM Informix]<br />
<br />
This wiki article says, "Informix is generally considered to be optimized for environments with very low or no database administration, including use as an embedded database. It has a long track record of supporting very high transaction rates and providing uptime characteristics needed for mission critical applications such as manufacturing lines and reservation systems. Informix has been widely deployed in the retail sector, where the low administration overhead makes it useful for in-store deployments."<br />
<br />
<br />
I have worked with Informix in a very large reservation system, insurance and manufacturing. I find the above statement very true.<br />
<br />
<br />
I am currently working with <font color="red"><b>Informix 9.40.FC7</b></font> on HP-UX 11.11 as mostly an adminisrator not a developer. I recently added an <font color="red"><b>Informix 12.10.FC7WE</b></font> replicated server on RHEL 7.3. I started with <font color="red"><b>MySQL 3.23</b></font> on Linux and <font color="red"><b>Informix C-ISAM</b></font> on DEC Ultrix (pre IBM).<br />
<br />
*onstat commands are predefined queries that pull from the shared memory, sysmaster database, system files, etc.&nbsp;&nbsp;They are not output in the best format for reading or joining with other data...so use the sysmaster database to create your own reports with SQL joins&nbsp;&nbsp;([[Informix Monitoring]])<br />
*Learn the sysmaster database...this database holds configurations and statistics<br />
*ESQL/C is very fast for accessing the database. I used it to create session monitoring tool (itop) which is like *nix "top" or MySQL "mytop"<br />
*dbacces (output is vertical if width if greater than 80 characters) and isql are horrible SQL clients...use something like open source [http://squirrel-sql.sourceforge.net/ SQuirreL] for most queries. But, if you want to query table between Informix servers you have to use Informix tools like dbacces and isql.<br />
*Every database has catalog tables that hold table, column, index information, etc. (select tabname from systables where tabid < 100;)<br />
*Find columns with SQL...SELECT tabname, syscolumns.* FROM systables, syscolumns WHERE systables.tabid = syscolumns.tabid AND tabname = 'table'; or with ANSI join SELECT t.tabname, c.* FROM systables t JOIN syscolumns c ON t.tabid = c.tabid;<br />
*Raw devices are faster which Informix uses very well<br />
*Optimize your statistics plan for better performance<br />
*HPL (High Performance Loader) is a very awkward GUI tool, but can unload and reload tables quicker using a raw data format<br />
*Create enough space for logical logging to prevent downtime if the tape fails. The engine will block transaction if these logs can't be backed up<br />
*Large tables can really slow down OLTP databases. So, archive tables that are OLTP.<br />
*A "dummy" archive, ontape -s -L 0...w/TAPEDEV set to /dev/null (in onconfig), must be done after some configuration changes<br />
*Our Informix 9.40.FC7, which is 64 bit, has a 2GiB file limitation writing to HP-UX 11.11's file system...not the actual database data files going to a tape or pipe. So 9.40 can not archive a large database to disk without going to tape or through a pipe. 12.10 does not have this issue.<br />
*The system log only stamps the log with the date when the first record of the day is written...then only a time stamp is on the records.&nbsp;&nbsp;In 12.10 set "MSG_DATE 1" in the onconfig file to get the date stamp on each record.<br />
*Try and size your initial extents large enough that the engine does not have to keep creating more extents. Multiple extents fragment your table spaces.<br />
*Informix date and time fields/functions are very different from MySQL<br />
*I really like some of Informix's SQL extensions...like "||" for concatenation, field[n,m] for substring, field matches( regexp ), first, etc.<br />
*Don't hit ctrl-c while starting the database (command oninit)...this will leave share memory in limbo<br />
*Informix can do queries between 2 servers.&nbsp;&nbsp;Use lowercase strings for DBSERVERNAME and DBSERVERALIASES values<br />
*Do not OS "nice" dbaccess, etc. The engine handles the priority. Set MAX_PDQPRIORITY (Parallel Database Query) to process queries faster.<br />
*Informix is closely tied to the OS. Users and passwords are created and maintained by the OS.<br />
*Informix privileges are definitely different from MySQL. Informix has a "connect" grant that I like because it is the only privilges you need to revoke to deny a user access make other grants void! Also, Informix can list "all" grants in one statement...MySQL can not!<br />
*<font color="red">Informix 12.10 has a single user mode...does MySQL? (read_only=1)</font><br />
*Informix has had descending btree indexes since 9.40, but MySQL will not have them until 8.0.<br />
*Informix "CURRENT" operator vs MySQL NOW() function.<br />
*Informix &lt;database&gt;<font color="red"><b>:</b></font>&lt;table&gt;...MySQL &lt;database&gt;<font color="red"><b>.</b></font>&lt;table&gt;<br />
*Informix 9.40 did not have a "truncate" command!<br />
<br />
<br />
What are the differences between SQL statements with Informix and MySQL?&nbsp;&nbsp;(<font color="green">positive</font>/<font color="red">negative</font>/<font color="orange">neutral</font>)<br />
<table><br />
<tr><br />
<td><br />
Informix<br />
</td><br />
<td><br />
MySQL<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
<font color="orange"><b>database</b></font> database;<br />
</td><br />
<td><br />
<font color="orange"><b>use</b></font> database;<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
comments are: "<font color="orange"><b>{</b></font>" comment(s) "<font color="orange"><b>}</b></font>" or "<font color="orange"><b>--</b></font>"<br />
</td><br />
<td><br />
coments are: "<font color="orange"><b>/*</b></font>" comment(s) "<font color="orange"><b>*/</b></font>" or "<font color="orange"><b>--</b></font>"<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
<font color="red">A table NEEDS to be included in ALL select statements</font><br />
</td><br />
<td><br />
<font color="green">A table DOES NOT NEED to be included in select statements</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green"><b>MATCHES</b></font> <i><b>'regular_expr'</b></i> FROM <i><b>table</b></i>;<br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="red"><b>REGEXP</b></font> <i><b>'regular_expr'</b></i>;<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green"><b>||</b></font> <i><b>'select_expr'</b></i> FROM <i><b>table</b></i>;<br />
</td><br />
<td><br />
SELECT <font color="red">CONCAT(</font> <i><b>'select_expr'</b></i>, <i><b>'select_expr'</b></i> <font color="red">)</font>;<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <font color="red">FIRST i</font> <i><b>'select_expr'</b></i> FROM <i><b>table</b></i>;<br />
<font color="blue"><b>--OR</b></font><br />
SELECT <i><b>'select_expr'</b></i> FROM <i><b>table</b></i> <font color="green">LIMIT i</font>; {Informix version 12}<br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green">LIMIT i</font>;<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> FROM <font color="red"><i><b>table</b></i> WHERE 1 = 1</font>;<br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green">WHERE 1</font>;<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'<font color="green">[i,j]</font></b></i> FROM <i><b>table</b></i> 1 = 1;<br />
</td><br />
<td><br />
SELECT <font color="red">SUBSTR(</font> <i><b>'select_expr', <font color="red">i, j )</font> </b></i>WHERE 1;<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <font color="red">CURRENT</font> FROM <i><b>systables</b></i> WHERE <i><b>tabid = 1</b></i>;<br />
</td><br />
<td><br />
SELECT <font color="green">NOW( )</font>;<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT * FROM <i><b>database</b></i><font color="orange"><b>:</b></font><i><b>table</b></i>;<br />
</td><br />
<td><br />
SELECT * FROM <i><b>database</b></i><font color="orange"><b>.</b></font><i><b>table</b></i>;<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>database</b></i>:systables.tabname, <i><b>database</b></i>:syscolumns.*<br />
FROM <i><b>database</b></i>:systables<br />
JOIN <i><b>database</b></i>:syscolumns<br />
ON <i><b>database</b></i>:systables.tabid = <i><b>database</b></i>:syscolumns.tabid<br />
WHERE <i><b>database</b></i>:systables.tabname = '<i><b>table</b></i>';<br />
</td><br />
<td><br />
SELECT * <br />
FROM information_schema.columns<br />
WHERE table_schema = '<i><b>database</b></i>' AND table_name = '<i><b>table</b></i>';<br />
<font color="blue"><b>--OR</b></font><br />
<font color="green">DESCRIBE <i><b>database</b></i>.<i><b>table</b></i>;</font><br />
</td><br />
</tr><br />
</table><br />
<br />
<br />
[http://www.iiug.org/en/2017/07/29/compare-informix/ Compare the Informix Version 12 editions]</div>Kemikohttps://wiki.kemiko.us/index.php?title=Idioms&diff=406Idioms2017-10-25T23:35:04Z<p>Kemiko: </p>
<hr />
<div><font size="+2">Plus similar items</font><br />
<br />
* 5% of a watermelon is better than 50% of a grape<br />
* Always in the last place (why would you keep looking)<br />
* (It cost) an arm and a leg<br />
* As sharp as a river rock<br />
* As the crow flies<br />
* Your bag (of tricks)<br />
* Boobing (not river tubing)<br />
* Birthday suit<br />
* Black swan<br />
* Bombshell<br />
* Chicken/egg<br />
* Comb-over<br />
* Control freak<br />
* Cool<br />
* Cold<br />
* Clean slate<br />
* Deep sh*t<br />
* Deer in the headlights<br />
* Don't sh*t where you eat<br />
* Duck<br />
* Everyone and their grandma<br />
* Fat fingers<br />
* Fine from afar, but far from fine<br />
* Fixed his wagon<br />
* Froggy (foggy)<br />
* Fudge factor<br />
* Glass ceiling<br />
* Great minds discuss ideas; average minds discuss events; small minds discuss people<br />
* Hart of [gold,stone]<br />
* Hollow leg<br />
* Hot<br />
* In the dog house<br />
* It is beyond me<br />
* It is raining cats and dogs<br />
* It is what it is<br />
* Keep an eye on it<br />
* Like a moth to the light<br />
* Meat salad (my Mongolian BBQ)<br />
* Monkey wrench<br />
* Nancy<br />
* Not the brightest bulb<br />
* Not the brightest crayon in the box<br />
* Not the sharpest tool in the shed<br />
* Numbskull<br />
* Out of sight...out of mind<br />
* Pencil Pusher<br />
* Pigskin<br />
* Poker face<br />
* Red herring<br />
* Right/Just around the corner<br />
* Sally<br />
* Saving for a rainy day<br />
* Slippery Slope<br />
* Smoking gun<br />
* Sneakernet<br />
* Snowflake<br />
* Spreadshits<br />
* Stink on shit<br />
* Straw man<br />
* Tool<br />
* Tunnel vision<br />
* Use your head for something other than a hat rack<br />
* White on rice<br />
* That's going to mess up my/your TIVO<br />
* Wally World<br />
* Wasting time<br />
* Watching the grass grow<br />
* Watching the paint dry<br />
* What happens in Vegas stays in Vegas<br />
* WTF - What the...(f*ck)<br />
* White lie<br />
* White on rice<br />
* You suck (d*ck)</div>Kemikohttps://wiki.kemiko.us/index.php?title=Idioms&diff=405Idioms2017-10-25T23:33:39Z<p>Kemiko: </p>
<hr />
<div><br />
== Plus similar items ==<br />
<br />
* 5% of a watermelon is better than 50% of a grape<br />
* Always in the last place (why would you keep looking)<br />
* (It cost) an arm and a leg<br />
* As sharp as a river rock<br />
* As the crow flies<br />
* Your bag (of tricks)<br />
* Boobing (not river tubing)<br />
* Birthday suit<br />
* Black swan<br />
* Bombshell<br />
* Chicken/egg<br />
* Comb-over<br />
* Control freak<br />
* Cool<br />
* Cold<br />
* Clean slate<br />
* Deep sh*t<br />
* Deer in the headlights<br />
* Don't sh*t where you eat<br />
* Duck<br />
* Everyone and their grandma<br />
* Fat fingers<br />
* Fine from afar, but far from fine<br />
* Fixed his wagon<br />
* Froggy (foggy)<br />
* Fudge factor<br />
* Glass ceiling<br />
* Great minds discuss ideas; average minds discuss events; small minds discuss people<br />
* Hart of [gold,stone]<br />
* Hollow leg<br />
* Hot<br />
* In the dog house<br />
* It is beyond me<br />
* It is raining cats and dogs<br />
* It is what it is<br />
* Keep an eye on it<br />
* Like a moth to the light<br />
* Meat salad (my Mongolian BBQ)<br />
* Monkey wrench<br />
* Nancy<br />
* Not the brightest bulb<br />
* Not the brightest crayon in the box<br />
* Not the sharpest tool in the shed<br />
* Numbskull<br />
* Out of sight...out of mind<br />
* Pencil Pusher<br />
* Pigskin<br />
* Poker face<br />
* Red herring<br />
* Right/Just around the corner<br />
* Sally<br />
* Saving for a rainy day<br />
* Slippery Slope<br />
* Smoking gun<br />
* Sneakernet<br />
* Snowflake<br />
* Spreadshits<br />
* Stink on shit<br />
* Straw man<br />
* Tool<br />
* Tunnel vision<br />
* Use your head for something other than a hat rack<br />
* White on rice<br />
* That's going to mess up my/your TIVO<br />
* Wally World<br />
* Wasting time<br />
* Watching the grass grow<br />
* Watching the paint dry<br />
* What happens in Vegas stays in Vegas<br />
* WTF - What the...(f*ck)<br />
* White lie<br />
* White on rice<br />
* You suck (d*ck)</div>Kemikohttps://wiki.kemiko.us/index.php?title=Idioms&diff=404Idioms2017-10-25T23:21:30Z<p>Kemiko: </p>
<hr />
<div>* 5% of a watermelon is better than 50% of a grape<br />
* Always in the last place (why would you keep looking)<br />
* (It cost) an arm and a leg<br />
* As sharp as a river rock<br />
* As the crow flies<br />
* Your bag (of tricks)<br />
* Boobing (not river tubing)<br />
* Birthday suit<br />
* Black swan<br />
* Bombshell<br />
* Chicken/egg<br />
* Comb-over<br />
* Control freak<br />
* Cool<br />
* Cold<br />
* Clean slate<br />
* Deep sh*t<br />
* Deer in the headlights<br />
* Don't sh*t where you eat<br />
* Duck<br />
* Everyone and their grandma<br />
* Fat fingers<br />
* Fine from afar, but far from fine<br />
* Fixed his wagon<br />
* Froggy (foggy)<br />
* Fudge factor<br />
* Glass ceiling<br />
* Great minds discuss ideas; average minds discuss events; small minds discuss people<br />
* Hart of [gold,stone]<br />
* Hollow leg<br />
* Hot<br />
* In the dog house<br />
* It is beyond me<br />
* It is raining cats and dogs<br />
* It is what it is<br />
* Keep an eye on it<br />
* Like a moth to the light<br />
* Meat salad (my Mongolian BBQ)<br />
* Monkey wrench<br />
* Nancy<br />
* Not the brightest bulb<br />
* Not the brightest crayon in the box<br />
* Not the sharpest tool in the shed<br />
* Numbskull<br />
* Out of sight...out of mind<br />
* Pencil Pusher<br />
* Pigskin<br />
* Poker face<br />
* Red herring<br />
* Right/Just around the corner<br />
* Sally<br />
* Saving for a rainy day<br />
* Slippery Slope<br />
* Smoking gun<br />
* Sneakernet<br />
* Snowflake<br />
* Spreadshits<br />
* Stink on shit<br />
* Straw man<br />
* Tool<br />
* Tunnel vision<br />
* Use your head for something other than a hat rack<br />
* White on rice<br />
* That's going to mess up my/your TIVO<br />
* Wally World<br />
* Wasting time<br />
* Watching the grass grow<br />
* Watching the paint dry<br />
* What happens in Vegas stays in Vegas<br />
* WTF - What the...(f*ck)<br />
* White lie<br />
* White on rice<br />
* You suck (d*ck)</div>Kemikohttps://wiki.kemiko.us/index.php?title=Informix&diff=403Informix2017-10-22T18:22:00Z<p>Kemiko: </p>
<hr />
<div>[https://en.wikipedia.org/wiki/IBM_Informix IBM Informix]<br />
<br />
This wiki article says, "Informix is generally considered to be optimized for environments with very low or no database administration, including use as an embedded database. It has a long track record of supporting very high transaction rates and providing uptime characteristics needed for mission critical applications such as manufacturing lines and reservation systems. Informix has been widely deployed in the retail sector, where the low administration overhead makes it useful for in-store deployments."<br />
<br />
<br />
I have worked with Informix in a very large reservation system, insurance and manufacturing. I find the above statement very true.<br />
<br />
<br />
I am currently working with <font color="red"><b>Informix 9.40.FC7</b></font> on HP-UX 11.11 as mostly an adminisrator not a developer. I recently added an <font color="red"><b>Informix 12.10.FC7WE</b></font> replicated server on RHEL 7.3. I started with <font color="red"><b>MySQL 3.23</b></font> on Linux and <font color="red"><b>Informix C-ISAM</b></font> on DEC Ultrix (pre IBM).<br />
<br />
*onstat commands are predefined queries that pull from the shared memory, sysmaster database, system files, etc.&nbsp;&nbsp;They are not output in the best format for reading or joining with other data...so use the sysmaster database to create your own reports with SQL joins&nbsp;&nbsp;([[Informix Monitoring]])<br />
*Learn the sysmaster database...this database holds configurations and statistics<br />
*ESQL/C is very fast for accessing the database. I used it to create session monitoring tool (itop) which is like *nix "top" or MySQL "mytop"<br />
*dbacces (output is vertical if width if greater than 80 characters) and isql are horrible SQL clients...use something like open source [http://squirrel-sql.sourceforge.net/ SQuirreL] for most queries. But, if you want to query table between Informix servers you have to use Informix tools like dbacces and isql.<br />
*Every database has catalog tables that hold table, column, index information, etc. (select tabname from systables where tabid < 100;)<br />
*Find columns with SQL...SELECT tabname, syscolumns.* FROM systables, syscolumns WHERE systables.tabid = syscolumns.tabid AND tabname = 'table'; or with ANSI join SELECT t.tabname, c.* FROM systables t JOIN syscolumns c ON t.tabid = c.tabid;<br />
*Raw devices are faster which Informix uses very well<br />
*Optimize your statistics plan for better performance<br />
*HPL (High Performance Loader) is a very awkward GUI tool, but can unload and reload tables quicker using a raw data format<br />
*Create enough space for logical logging to prevent downtime if the tape fails. The engine will block transaction if these logs can't be backed up<br />
*Large tables can really slow down OLTP databases. So, archive tables that are OLTP.<br />
*A "dummy" archive, ontape -s -L 0...w/TAPEDEV set to /dev/null (in onconfig), must be done after some configuration changes<br />
*Our Informix 9.40.FC7, which is 64 bit, has a 2GiB file limitation writing to HP-UX 11.11's file system...not the actual database data files going to a tape or pipe. So 9.40 can not archive a large database to disk without going to tape or through a pipe. 12.10 does not have this issue.<br />
*The system log only stamps the log with the date when the first record of the day is written...then only a time stamp is on the records.&nbsp;&nbsp;In 12.10 set "MSG_DATE 1" in the onconfig file to get the date stamp on each record.<br />
*Try and size your initial extents large enough that the engine does not have to keep creating more extents. Multiple extents fragment your table spaces.<br />
*Informix date and time fields/functions are very different from MySQL<br />
*I really like some of Informix's SQL extensions...like "||" for concatenation, field[n,m] for substring, field matches( regexp ), first, etc.<br />
*Don't hit ctrl-c while starting the database (command oninit)...this will leave share memory in limbo<br />
*Informix can do queries between 2 servers.&nbsp;&nbsp;Use lowercase strings for DBSERVERNAME and DBSERVERALIASES values<br />
*Do not OS "nice" dbaccess, etc. The engine handles the priority. Set MAX_PDQPRIORITY (Parallel Database Query) to process queries faster.<br />
*Informix is closely tied to the OS. Users and passwords are created and maintained by the OS.<br />
*Informix privileges are definitely different from MySQL. Informix has a "connect" grant that I like because it is the only privilges you need to revoke to deny a user access make other grants void! Also, Informix can list "all" grants in one statement...MySQL can not!<br />
*<font color="red">Informix 12.10 has a single user mode...does MySQL? (read_only=1)</font><br />
*Informix has had descending btree indexes since 9.40, but MySQL will not have them until 8.0.<br />
*Informix "CURRENT" operator vs MySQL NOW() function.<br />
*Informix &lt;database&gt;<font color="red"><b>:</b></font>&lt;table&gt;...MySQL &lt;database&gt;<font color="red"><b>.</b></font>&lt;table&gt;<br />
<br />
<br />
What are the differences between SQL statements with Informix and MySQL?&nbsp;&nbsp;(<font color="green">positive</font>/<font color="red">negative</font>/<font color="orange">neutral</font>)<br />
<table><br />
<tr><br />
<td><br />
Informix<br />
</td><br />
<td><br />
MySQL<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
<font color="orange"><b>database</b></font> database;<br />
</td><br />
<td><br />
<font color="orange"><b>use</b></font> database;<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
comments are: "<font color="orange"><b>{</b></font>" comment(s) "<font color="orange"><b>}</b></font>" or "<font color="orange"><b>--</b></font>"<br />
</td><br />
<td><br />
coments are: "<font color="orange"><b>/*</b></font>" comment(s) "<font color="orange"><b>*/</b></font>" or "<font color="orange"><b>--</b></font>"<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
<font color="red">A table NEEDS to be included in ALL select statements</font><br />
</td><br />
<td><br />
<font color="green">A table DOES NOT NEED to be included in select statements</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green"><b>MATCHES</b></font> <i><b>'regular_expr'</b></i> FROM <i><b>table</b></i>;<br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="red"><b>REGEXP</b></font> <i><b>'regular_expr'</b></i>;<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green"><b>||</b></font> <i><b>'select_expr'</b></i> FROM <i><b>table</b></i>;<br />
</td><br />
<td><br />
SELECT <font color="red">CONCAT(</font> <i><b>'select_expr'</b></i>, <i><b>'select_expr'</b></i> <font color="red">)</font>;<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <font color="red">FIRST i</font> <i><b>'select_expr'</b></i> FROM <i><b>table</b></i>;<br />
<font color="blue"><b>--OR</b></font><br />
SELECT <i><b>'select_expr'</b></i> FROM <i><b>table</b></i> <font color="green">LIMIT i</font>; {Informix version 12}<br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green">LIMIT i</font>;<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> FROM <font color="red"><i><b>table</b></i> WHERE 1 = 1</font>;<br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green">WHERE 1</font>;<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'<font color="green">[i,j]</font></b></i> FROM <i><b>table</b></i> 1 = 1;<br />
</td><br />
<td><br />
SELECT <font color="red">SUBSTR(</font> <i><b>'select_expr', <font color="red">i, j )</font> </b></i>WHERE 1;<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <font color="red">CURRENT</font> FROM <i><b>systables</b></i> WHERE <i><b>tabid = 1</b></i>;<br />
</td><br />
<td><br />
SELECT <font color="green">NOW( )</font>;<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT * FROM <i><b>database</b></i><font color="orange"><b>:</b></font><i><b>table</b></i>;<br />
</td><br />
<td><br />
SELECT * FROM <i><b>database</b></i><font color="orange"><b>.</b></font><i><b>table</b></i>;<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>database</b></i>:systables.tabname, <i><b>database</b></i>:syscolumns.*<br />
FROM <i><b>database</b></i>:systables<br />
JOIN <i><b>database</b></i>:syscolumns<br />
ON <i><b>database</b></i>:systables.tabid = <i><b>database</b></i>:syscolumns.tabid<br />
WHERE <i><b>database</b></i>:systables.tabname = '<i><b>table</b></i>';<br />
</td><br />
<td><br />
SELECT * <br />
FROM information_schema.columns<br />
WHERE table_schema = '<i><b>database</b></i>' AND table_name = '<i><b>table</b></i>';<br />
<font color="blue"><b>--OR</b></font><br />
<font color="green">DESCRIBE <i><b>database</b></i>.<i><b>table</b></i>;</font><br />
</td><br />
</tr><br />
</table><br />
<br />
<br />
[http://www.iiug.org/en/2017/07/29/compare-informix/ Compare the Informix Version 12 editions]</div>Kemikohttps://wiki.kemiko.us/index.php?title=Informix&diff=402Informix2017-10-21T19:58:26Z<p>Kemiko: </p>
<hr />
<div>[https://en.wikipedia.org/wiki/IBM_Informix IBM Informix]<br />
<br />
This wiki article says, "Informix is generally considered to be optimized for environments with very low or no database administration, including use as an embedded database. It has a long track record of supporting very high transaction rates and providing uptime characteristics needed for mission critical applications such as manufacturing lines and reservation systems. Informix has been widely deployed in the retail sector, where the low administration overhead makes it useful for in-store deployments."<br />
<br />
<br />
I have worked with Informix in a very large reservation system, insurance and manufacturing. I find the above statement very true.<br />
<br />
<br />
I am currently working with <font color="red"><b>Informix 9.40.FC7</b></font> on HP-UX 11.11 as mostly an adminisrator not a developer. I recently added an <font color="red"><b>Informix 12.10.FC7WE</b></font> replicated server on RHEL 7.3. I started with <font color="red"><b>MySQL 3.23</b></font> on Linux and <font color="red"><b>Informix C-ISAM</b></font> on DEC Ultrix.<br />
<br />
*onstat commands are predefined queries that pull from the shared memory, sysmaster database, system files, etc.&nbsp;&nbsp;They are not output in the best format for reading or joining with other data...so use the sysmaster database to create your own reports with SQL joins&nbsp;&nbsp;([[Informix Monitoring]])<br />
*Learn the sysmaster database...this database holds configurations and statistics<br />
*ESQL/C is very fast for accessing the database. I used it to create session monitoring tool (itop) which is like *nix "top" or MySQL "mytop"<br />
*dbacces (output is vertical if width if greater than 80 characters) and isql are horrible SQL clients...use something like open source [http://squirrel-sql.sourceforge.net/ SQuirreL] for most queries. But, if you want to query table between Informix servers you have to use Informix tools like dbacces and isql.<br />
*Every database has catalog tables that hold table, column, index information, etc. (select tabname from systables where tabid < 100;)<br />
*Find columns with SQL...SELECT tabname, syscolumns.* FROM systables, syscolumns WHERE systables.tabid = syscolumns.tabid AND tabname = 'table'; or with ANSI join SELECT t.tabname, c.* FROM systables t JOIN syscolumns c ON t.tabid = c.tabid;<br />
*Raw devices are faster which Informix uses very well<br />
*Optimize your statistics plan for better performance<br />
*HPL (High Performance Loader) is a very awkward GUI tool, but can unload and reload tables quicker using a raw data format<br />
*Create enough space for logical logging to prevent downtime if the tape fails. The engine will block transaction if these logs can't be backed up<br />
*Large tables can really slow down OLTP databases. So, archive tables that are OLTP.<br />
*A "dummy" archive, ontape -s -L 0...w/TAPEDEV set to /dev/null (in onconfig), must be done after some configuration changes<br />
*Our Informix 9.40.FC7, which is 64 bit, has a 2GiB file limitation writing to HP-UX 11.11's file system...not the actual database data files going to a tape or pipe. So 9.40 can not archive a large database to disk without going to tape or through a pipe. 12.10 does not have this issue.<br />
*The system log only stamps the log with the date when the first record of the day is written...then only a time stamp is on the records.&nbsp;&nbsp;In 12.10 set "MSG_DATE 1" in the onconfig file to get the date stamp on each record.<br />
*Try and size your initial extents large enough that the engine does not have to keep creating more extents. Multiple extents fragment your table spaces.<br />
*Informix date and time fields/functions are very different from MySQL<br />
*I really like some of Informix's SQL extensions...like "||" for concatenation, field[n,m] for substring, field matches( regexp ), first, etc.<br />
*Don't hit ctrl-c while starting the database (command oninit)...this will leave share memory in limbo<br />
*Informix can do queries between 2 servers.&nbsp;&nbsp;Use lowercase strings for DBSERVERNAME and DBSERVERALIASES values<br />
*Do not OS "nice" dbaccess, etc. The engine handles the priority. Set MAX_PDQPRIORITY (Parallel Database Query) to process queries faster.<br />
*Informix is closely tied to the OS. Users and passwords are created and maintained by the OS.<br />
*Informix privileges are definitely different from MySQL. Informix has a "connect" grant that I like because it is the only privilges you need to revoke to deny a user access make other grants void! Also, Informix can list "all" grants in one statement...MySQL can not!<br />
*<font color="red">Informix 12.10 has a single user mode...does MySQL? (read_only=1)</font><br />
*Informix has had descending btree indexes since 9.40, but MySQL will not have them until 8.0.<br />
*Informix "CURRENT" operator vs MySQL NOW() function.<br />
*Informix &lt;database&gt;<font color="red"><b>:</b></font>&lt;table&gt;...MySQL &lt;database&gt;<font color="red"><b>.</b></font>&lt;table&gt;<br />
<br />
<br />
What are the differences between SQL statements with Informix and MySQL?&nbsp;&nbsp;(<font color="green">positive</font>/<font color="red">negative</font>/<font color="orange">neutral</font>)<br />
<table><br />
<tr><br />
<td><br />
Informix<br />
</td><br />
<td><br />
MySQL<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
<font color="orange"><b>database</b></font> database;<br />
</td><br />
<td><br />
<font color="orange"><b>use</b></font> database;<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
comments are: "<font color="orange"><b>{</b></font>" comment(s) "<font color="orange"><b>}</b></font>" or "<font color="orange"><b>--</b></font>"<br />
</td><br />
<td><br />
coments are: "<font color="orange"><b>/*</b></font>" comment(s) "<font color="orange"><b>*/</b></font>" or "<font color="orange"><b>--</b></font>"<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
<font color="red">A table NEEDS to be included in ALL select statements</font><br />
</td><br />
<td><br />
<font color="green">A table DOES NOT NEED to be included in select statements</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green"><b>MATCHES</b></font> <i><b>'regular_expr'</b></i> FROM <i><b>table</b></i>;<br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="red"><b>REGEXP</b></font> <i><b>'regular_expr'</b></i>;<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green"><b>||</b></font> <i><b>'select_expr'</b></i> FROM <i><b>table</b></i>;<br />
</td><br />
<td><br />
SELECT <font color="red">CONCAT(</font> <i><b>'select_expr'</b></i>, <i><b>'select_expr'</b></i> <font color="red">)</font>;<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <font color="red">FIRST i</font> <i><b>'select_expr'</b></i> FROM <i><b>table</b></i>;<br />
<font color="blue"><b>--OR</b></font><br />
SELECT <i><b>'select_expr'</b></i> FROM <i><b>table</b></i> <font color="green">LIMIT i</font>; {Informix version 12}<br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green">LIMIT i</font>;<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> FROM <font color="red"><i><b>table</b></i> WHERE 1 = 1</font>;<br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green">WHERE 1</font>;<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'<font color="green">[i,j]</font></b></i> FROM <i><b>table</b></i> 1 = 1;<br />
</td><br />
<td><br />
SELECT <font color="red">SUBSTR(</font> <i><b>'select_expr', <font color="red">i, j )</font> </b></i>WHERE 1;<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <font color="red">CURRENT</font> FROM <i><b>systables</b></i> WHERE <i><b>tabid = 1</b></i>;<br />
</td><br />
<td><br />
SELECT <font color="green">NOW( )</font>;<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT * FROM <i><b>database</b></i><font color="orange"><b>:</b></font><i><b>table</b></i>;<br />
</td><br />
<td><br />
SELECT * FROM <i><b>database</b></i><font color="orange"><b>.</b></font><i><b>table</b></i>;<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>database</b></i>:systables.tabname, <i><b>database</b></i>:syscolumns.*<br />
FROM <i><b>database</b></i>:systables<br />
JOIN <i><b>database</b></i>:syscolumns<br />
ON <i><b>database</b></i>:systables.tabid = <i><b>database</b></i>:syscolumns.tabid<br />
WHERE <i><b>database</b></i>:systables.tabname = '<i><b>table</b></i>';<br />
</td><br />
<td><br />
SELECT * <br />
FROM information_schema.columns<br />
WHERE table_schema = '<i><b>database</b></i>' AND table_name = '<i><b>table</b></i>';<br />
<font color="blue"><b>--OR</b></font><br />
<font color="green">DESCRIBE <i><b>database</b></i>.<i><b>table</b></i>;</font><br />
</td><br />
</tr><br />
</table><br />
<br />
<br />
[http://www.iiug.org/en/2017/07/29/compare-informix/ Compare the Informix Version 12 editions]</div>Kemikohttps://wiki.kemiko.us/index.php?title=Informix&diff=401Informix2017-10-21T18:51:03Z<p>Kemiko: </p>
<hr />
<div>[https://en.wikipedia.org/wiki/IBM_Informix IBM Informix]<br />
<br />
This wiki article says, "Informix is generally considered to be optimized for environments with very low or no database administration, including use as an embedded database. It has a long track record of supporting very high transaction rates and providing uptime characteristics needed for mission critical applications such as manufacturing lines and reservation systems. Informix has been widely deployed in the retail sector, where the low administration overhead makes it useful for in-store deployments."<br />
<br />
<br />
I have worked with Informix in a very large reservation system, insurance and manufacturing. I find the above statement very true.<br />
<br />
<br />
I am currently working with <font color="red"><b>Informix 9.40.FC7</b></font> on HP-UX 11.11 as mostly an adminisrator not a developer. I recently added an <font color="red"><b>Informix 12.10.FC7WE</b></font> replicated server on RHEL 7.3. I started with <font color="red"><b>MySQL 3.23</b></font> on Linux and <font color="red"><b>Informix C-ISAM</b></font> on DEC Ultrix.<br />
<br />
*onstat commands are predefined queries that pull from the shared memory, sysmaster database, system files, etc.&nbsp;&nbsp;They are not output in the best format for reading or joining with other data...so use the sysmaster database to create your own reports with SQL joins&nbsp;&nbsp;([[Informix Monitoring]])<br />
*Learn the sysmaster database...this database holds configurations and statistics<br />
*ESQL/C is very fast for accessing the database. I used it to create session monitoring tool (itop) which is like *nix "top" or MySQL "mytop"<br />
*dbacces (output is vertical if width if greater than 80 characters) and isql are horrible SQL clients...use something like open source [http://squirrel-sql.sourceforge.net/ SQuirreL] for most queries. But, if you want to query table between Informix servers you have to use Informix tools like dbacces and isql.<br />
*Every database has catalog tables that hold table, column, index information, etc. (select tabname from systables where tabid < 100;)<br />
*Find columns with SQL...SELECT tabname, syscolumns.* FROM systables, syscolumns WHERE systables.tabid = syscolumns.tabid AND tabname = 'table'; or with ANSI join SELECT t.tabname, c.* FROM systables t JOIN syscolumns c ON t.tabid = c.tabid;<br />
*Raw devices are faster which Informix uses very well<br />
*Optimize your statistics plan for better performance<br />
*HPL (High Performance Loader) is a very awkward GUI tool, but can unload and reload tables quicker using a raw data format<br />
*Create enough space for logical logging to prevent downtime if the tape fails. The engine will block transaction if these logs can't be backed up<br />
*Large tables can really slow down OLTP databases. So, archive tables that are OLTP.<br />
*A "dummy" archive, ontape -s -L 0...w/TAPEDEV set to /dev/null (in onconfig), must be done after some configuration changes<br />
*Our Informix 9.40.FC7, which is 64 bit, has a 2GiB file limitation writing to HP-UX 11.11's file system...not the actual database data files going to a tape or pipe. So 9.40 can not archive a large database to disk without going to tape or through a pipe. 12.10 does not have this issue.<br />
*The system log only stamps the log with the date when the first record of the day is written...then only a time stamp is on the records.&nbsp;&nbsp;In 12.10 set "MSG_DATE 1" in the onconfig file to get the date stamp on each record.<br />
*Try and size your initial extents large enough that the engine does not have to keep creating more extents. Multiple extents fragment your table spaces.<br />
*Informix date and time fields/functions are very different from MySQL<br />
*I really like some of Informix's SQL extensions...like "||" for concatenation, field[n,m] for substring, field matches( regexp ), first, etc.<br />
*Don't hit ctrl-c while starting the database (command oninit)...this will leave share memory in limbo<br />
*Informix can do queries between 2 servers.&nbsp;&nbsp;Use lowercase strings for DBSERVERNAME and DBSERVERALIASES values<br />
*Do not OS "nice" dbaccess, etc. The engine handles the priority. Set MAX_PDQPRIORITY (Parallel Database Query) to process queries faster.<br />
*Informix is closely tied to the OS. Users and passwords are created and maintained by the OS.<br />
*Informix privileges are definitely different from MySQL. Informix has a "connect" grant that I like because it is the only privilges you need to revoke to deny a user access make other grants void! Also, Informix can list "all" grants in one statement...MySQL can not!<br />
*<font color="red">Informix 12.10 has a single user mode...does MySQL? (read_only=1)</font><br />
*Informix has had descending btree indexes since 9.40, but MySQL will not have them until 8.0.<br />
*Informix "CURRENT" operator vs MySQL NOW() function.<br />
*Informix &lt;database&gt;<font color="red"><b>:</b></font>&lt;table&gt;...MySQL &lt;database&gt;<font color="red"><b>.</b></font>&lt;table&gt;<br />
<br />
<br />
What are the differences between SQL statements with Informix and MySQL?&nbsp;&nbsp;(<font color="green">positive</font>/<font color="red">negative</font>/<font color="orange">neutral</font>)<br />
<table><br />
<tr><br />
<td><br />
Informix<br />
</td><br />
<td><br />
MySQL<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
<font color="orange"><b>database</b></font> database;<br />
</td><br />
<td><br />
<font color="orange"><b>use</b></font> database;<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
comments are: "<font color="orange"><b>{</b></font>" comment(s) "<font color="orange"><b>}</b></font>" or "<font color="orange"><b>--</b></font>"<br />
</td><br />
<td><br />
coments are: "<font color="orange"><b>/*</b></font>" comment(s) "<font color="orange"><b>*/</b></font>" or "<font color="orange"><b>--</b></font>"<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
<font color="red">A table NEEDS to be included in ALL select statements</font><br />
</td><br />
<td><br />
<font color="green">A table DOES NOT NEED to be included in select statements</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green"><b>MATCHES</b></font> <i><b>'regular_expr'</b></i> FROM <i><b>table</b></i><br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="red"><b>REGEXP</b></font> <i><b>'regular_expr'</b></i><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green"><b>||</b></font> <i><b>'select_expr'</b></i> FROM <i><b>table</b></i><br />
</td><br />
<td><br />
SELECT <font color="red">CONCAT(</font> <i><b>'select_expr'</b></i>, <i><b>'select_expr'</b></i> <font color="red">)</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <font color="red">FIRST i</font> <i><b>'select_expr'</b></i> FROM <i><b>table</b></i><br />
<font color="red"><b>OR</b></font><br />
SELECT <i><b>'select_expr'</b></i> FROM <i><b>table</b></i> <font color="green">LIMIT i</font>; {Informix version 12}<br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green">LIMIT i</font>;<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> FROM <font color="red"><i><b>table</b></i> WHERE 1 = 1</font><br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green">WHERE 1</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr<font color="green">[i,j]</font>'</b></i> FROM <i><b>table</b></i> 1 = 1<br />
</td><br />
<td><br />
SELECT <font color="red">SUBSTR(</font> <i><b>'select_expr', <font color="red">i, j )</font> </b></i>WHERE 1<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <font color="red">CURRENT</font> FROM <i><b>systables</b></i> WHERE <i><b>tabid = 1</b></i><br />
</td><br />
<td><br />
SELECT <font color="green">NOW( )</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT * FROM <i><b>database</b></i><font color="orange"><b>:</b></font><i><b>table</b></i><br />
</td><br />
<td><br />
SELECT * FROM <i><b>database</b></i><font color="orange"><b>.</b></font><i><b>table</b></i><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>database</b></i>:systables.tabname, <i><b>database</b></i>:syscolumns.*<br />
FROM <i><b>database</b></i>:systables<br />
JOIN <i><b>database</b></i>:syscolumns<br />
ON <i><b>database</b></i>:systables.tabid = <i><b>database</b></i>:syscolumns.tabid<br />
WHERE <i><b>database</b></i>:systables.tabname = '<i><b>table</b></i>';<br />
</td><br />
<td><br />
SELECT * FROM information_schema.columns WHERE table_schema = '<i><b>database</b></i>' AND table_name = '<i><b>table</b></i>';<br />
<font color="red"><b>OR</b></font><br />
<font color="green">DESCRIBE <i><b>database</b></i>.<i><b>table</b></i>;</font><br />
</td><br />
</tr><br />
</table><br />
<br />
<br />
[http://www.iiug.org/en/2017/07/29/compare-informix/ Compare the Informix Version 12 editions]</div>Kemikohttps://wiki.kemiko.us/index.php?title=Informix&diff=400Informix2017-10-21T18:39:35Z<p>Kemiko: </p>
<hr />
<div>[https://en.wikipedia.org/wiki/IBM_Informix IBM Informix]<br />
<br />
This wiki article says, "Informix is generally considered to be optimized for environments with very low or no database administration, including use as an embedded database. It has a long track record of supporting very high transaction rates and providing uptime characteristics needed for mission critical applications such as manufacturing lines and reservation systems. Informix has been widely deployed in the retail sector, where the low administration overhead makes it useful for in-store deployments."<br />
<br />
<br />
I have worked with Informix in a very large reservation system, insurance and manufacturing. I find the above statement very true.<br />
<br />
<br />
I am currently working with <font color="red"><b>Informix 9.40.FC7</b></font> on HP-UX 11.11 as mostly an adminisrator not a developer. I recently added an <font color="red"><b>Informix 12.10.FC7WE</b></font> replicated server on RHEL 7.3. I started with <font color="red"><b>MySQL 3.23</b></font> on Linux and <font color="red"><b>Informix C-ISAM</b></font> on DEC Ultrix.<br />
<br />
*onstat commands are predefined queries that pull from the shared memory, sysmaster database, system files, etc.&nbsp;&nbsp;They are not output in the best format for reading or joining with other data...so use the sysmaster database to create your own reports with SQL joins&nbsp;&nbsp;([[Informix Monitoring]])<br />
*Learn the sysmaster database...this database holds configurations and statistics<br />
*ESQL/C is very fast for accessing the database. I used it to create session monitoring tool (itop) which is like *nix "top" or MySQL "mytop"<br />
*dbacces (output is vertical if width if greater than 80 characters) and isql are horrible SQL clients...use something like open source [http://squirrel-sql.sourceforge.net/ SQuirreL] for most queries. But, if you want to query table between Informix servers you have to use Informix tools like dbacces and isql.<br />
*Every database has catalog tables that hold table, column, index information, etc. (select tabname from systables where tabid < 100;)<br />
*Find columns with SQL...SELECT tabname, syscolumns.* FROM systables, syscolumns WHERE systables.tabid = syscolumns.tabid AND tabname = 'table'; or with ANSI join SELECT t.tabname, c.* FROM systables t JOIN syscolumns c ON t.tabid = c.tabid;<br />
*Raw devices are faster which Informix uses very well<br />
*Optimize your statistics plan for better performance<br />
*HPL (High Performance Loader) is a very awkward GUI tool, but can unload and reload tables quicker using a raw data format<br />
*Create enough space for logical logging to prevent downtime if the tape fails. The engine will block transaction if these logs can't be backed up<br />
*Large tables can really slow down OLTP databases. So, archive tables that are OLTP.<br />
*A "dummy" archive, ontape -s -L 0...w/TAPEDEV set to /dev/null (in onconfig), must be done after some configuration changes<br />
*Our Informix 9.40.FC7, which is 64 bit, has a 2GiB file limitation writing to HP-UX 11.11's file system...not the actual database data files going to a tape or pipe. So 9.40 can not archive a large database to disk without going to tape or through a pipe. 12.10 does not have this issue.<br />
*The system log only stamps the log with the date when the first record of the day is written...then only a time stamp is on the records.&nbsp;&nbsp;In 12.10 set "MSG_DATE 1" in the onconfig file to get the date stamp on each record.<br />
*Try and size your initial extents large enough that the engine does not have to keep creating more extents. Multiple extents fragment your table spaces.<br />
*Informix date and time fields/functions are very different from MySQL<br />
*I really like some of Informix's SQL extensions...like "||" for concatenation, field[n,m] for substring, field matches( regexp ), first, etc.<br />
*Don't hit ctrl-c while starting the database (command oninit)...this will leave share memory in limbo<br />
*Informix can do queries between 2 servers.&nbsp;&nbsp;Use lowercase strings for DBSERVERNAME and DBSERVERALIASES values<br />
*Do not OS "nice" dbaccess, etc. The engine handles the priority. Set MAX_PDQPRIORITY (Parallel Database Query) to process queries faster.<br />
*Informix is closely tied to the OS. Users and passwords are created and maintained by the OS.<br />
*Informix privileges are definitely different from MySQL. Informix has a "connect" grant that I like because it is the only privilges you need to revoke to deny a user access make other grants void! Also, Informix can list "all" grants in one statement...MySQL can not!<br />
*<font color="red">Informix 12.10 has a single user mode...does MySQL? (read_only=1)</font><br />
*Informix has had descending btree indexes since 9.40, but MySQL will not have them until 8.0.<br />
*Informix "CURRENT" operator vs MySQL NOW() function.<br />
*Informix &lt;database&gt;<font color="red"><b>:</b></font>&lt;table&gt;...MySQL &lt;database&gt;<font color="red"><b>.</b></font>&lt;table&gt;<br />
<br />
<br />
What are the differences between SQL statements with Informix and MySQL?&nbsp;&nbsp;(<font color="green">positive</font>/<font color="red">negative</font>/<font color="orange">neutral</font>)<br />
<table><br />
<tr><br />
<td><br />
Informix<br />
</td><br />
<td><br />
MySQL<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
<font color="orange"><b>database</b></font> database;<br />
</td><br />
<td><br />
<font color="orange"><b>use</b></font> database;<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
comments are: "<font color="orange"><b>{</b></font>" comment(s) "<font color="orange"><b>}</b></font>" or "<font color="orange"><b>--</b></font>"<br />
</td><br />
<td><br />
coments are: "<font color="orange"><b>/*</b></font>" comment(s) "<font color="orange"><b>*/</b></font>" or "<font color="orange"><b>--</b></font>"<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
<font color="red">A table NEEDS to be included in ALL select statements</font><br />
</td><br />
<td><br />
<font color="green">A table DOES NOT NEED to be included in select statements</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green"><b>MATCHES</b></font> <i><b>'regular_expr'</b></i> FROM <i><b>table</b></i><br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="red"><b>REGEXP</b></font> <i><b>'regular_expr'</b></i><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green"><b>||</b></font> <i><b>'select_expr'</b></i> FROM <i><b>table</b></i><br />
</td><br />
<td><br />
SELECT <font color="red">CONCAT(</font> <i><b>'select_expr'</b></i>, <i><b>'select_expr'</b></i> <font color="red">)</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <font color="red">FIRST i</font> <i><b>'select_expr'</b></i> FROM <i><b>table</b></i><br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green">LIMIT i</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> FROM <font color="red"><i><b>table</b></i> WHERE 1 = 1</font><br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green">WHERE 1</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr<font color="green">[i,j]</font>'</b></i> FROM <i><b>table</b></i> 1 = 1<br />
</td><br />
<td><br />
SELECT <font color="red">SUBSTR(</font> <i><b>'select_expr', <font color="red">i, j )</font> </b></i>WHERE 1<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <font color="red">CURRENT</font> FROM <i><b>systables</b></i> WHERE <i><b>tabid = 1</b></i><br />
</td><br />
<td><br />
SELECT <font color="green">NOW( )</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT * FROM <i><b>database</b></i><font color="orange"><b>:</b></font><i><b>table</b></i><br />
</td><br />
<td><br />
SELECT * FROM <i><b>database</b></i><font color="orange"><b>.</b></font><i><b>table</b></i><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>database</b></i>:systables.tabname, <i><b>database</b></i>:syscolumns.*<br />
FROM <i><b>database</b></i>:systables<br />
JOIN <i><b>database</b></i>:syscolumns<br />
ON <i><b>database</b></i>:systables.tabid = <i><b>database</b></i>:syscolumns.tabid<br />
WHERE <i><b>database</b></i>:systables.tabname = '<i><b>table</b></i>';<br />
</td><br />
<td><br />
SELECT * FROM information_schema.columns WHERE table_schema = '<i><b>database</b></i>' AND table_name = '<i><b>table</b></i>';<br />
<font color="red"><b>OR</b></font><br />
DESCRIBE <i><b>database</b></i>.<i><b>table</b></i>;<br />
</td><br />
</tr><br />
</table><br />
<br />
<br />
[http://www.iiug.org/en/2017/07/29/compare-informix/ Compare the Informix Version 12 editions]</div>Kemikohttps://wiki.kemiko.us/index.php?title=Informix&diff=399Informix2017-10-21T18:33:56Z<p>Kemiko: </p>
<hr />
<div>[https://en.wikipedia.org/wiki/IBM_Informix IBM Informix]<br />
<br />
This wiki article says, "Informix is generally considered to be optimized for environments with very low or no database administration, including use as an embedded database. It has a long track record of supporting very high transaction rates and providing uptime characteristics needed for mission critical applications such as manufacturing lines and reservation systems. Informix has been widely deployed in the retail sector, where the low administration overhead makes it useful for in-store deployments."<br />
<br />
<br />
I have worked with Informix in a very large reservation system, insurance and manufacturing. I find the above statement very true.<br />
<br />
<br />
I am currently working with <font color="red"><b>Informix 9.40.FC7</b></font> on HP-UX 11.11 as mostly an adminisrator not a developer. I recently added an <font color="red"><b>Informix 12.10.FC7WE</b></font> replicated server on RHEL 7.3. I started with <font color="red"><b>MySQL 3.23</b></font> on Linux and <font color="red"><b>Informix C-ISAM</b></font> on DEC Ultrix.<br />
<br />
*onstat commands are predefined queries that pull from the shared memory, sysmaster database, system files, etc.&nbsp;&nbsp;They are not output in the best format for reading or joining with other data...so use the sysmaster database to create your own reports with SQL joins&nbsp;&nbsp;([[Informix Monitoring]])<br />
*Learn the sysmaster database...this database holds configurations and statistics<br />
*ESQL/C is very fast for accessing the database. I used it to create session monitoring tool (itop) which is like *nix "top" or MySQL "mytop"<br />
*dbacces (output is vertical if width if greater than 80 characters) and isql are horrible SQL clients...use something like open source [http://squirrel-sql.sourceforge.net/ SQuirreL] for most queries. But, if you want to query table between Informix servers you have to use Informix tools like dbacces and isql.<br />
*Every database has catalog tables that hold table, column, index information, etc. (select tabname from systables where tabid < 100;)<br />
*Find columns with SQL...SELECT tabname, syscolumns.* FROM systables, syscolumns WHERE systables.tabid = syscolumns.tabid AND tabname = 'table'; or with ANSI join SELECT t.tabname, c.* FROM systables t JOIN syscolumns c ON t.tabid = c.tabid;<br />
*Raw devices are faster which Informix uses very well<br />
*Optimize your statistics plan for better performance<br />
*HPL (High Performance Loader) is a very awkward GUI tool, but can unload and reload tables quicker using a raw data format<br />
*Create enough space for logical logging to prevent downtime if the tape fails. The engine will block transaction if these logs can't be backed up<br />
*Large tables can really slow down OLTP databases. So, archive tables that are OLTP.<br />
*A "dummy" archive, ontape -s -L 0...w/TAPEDEV set to /dev/null (in onconfig), must be done after some configuration changes<br />
*Our Informix 9.40.FC7, which is 64 bit, has a 2GiB file limitation writing to HP-UX 11.11's file system...not the actual database data files going to a tape or pipe. So 9.40 can not archive a large database to disk without going to tape or through a pipe. 12.10 does not have this issue.<br />
*The system log only stamps the log with the date when the first record of the day is written...then only a time stamp is on the records.&nbsp;&nbsp;In 12.10 set "MSG_DATE 1" in the onconfig file to get the date stamp on each record.<br />
*Try and size your initial extents large enough that the engine does not have to keep creating more extents. Multiple extents fragment your table spaces.<br />
*Informix date and time fields/functions are very different from MySQL<br />
*I really like some of Informix's SQL extensions...like "||" for concatenation, field[n,m] for substring, field matches( regexp ), first, etc.<br />
*Don't hit ctrl-c while starting the database (command oninit)...this will leave share memory in limbo<br />
*Informix can do queries between 2 servers.&nbsp;&nbsp;Use lowercase strings for DBSERVERNAME and DBSERVERALIASES values<br />
*Do not OS "nice" dbaccess, etc. The engine handles the priority. Set MAX_PDQPRIORITY (Parallel Database Query) to process queries faster.<br />
*Informix is closely tied to the OS. Users and passwords are created and maintained by the OS.<br />
*Informix privileges are definitely different from MySQL. Informix has a "connect" grant that I like because it is the only privilges you need to revoke to deny a user access make other grants void! Also, Informix can list "all" grants in one statement...MySQL can not!<br />
*<font color="red">Informix 12.10 has a single user mode...does MySQL? (read_only=1)</font><br />
*Informix has had descending btree indexes since 9.40, but MySQL will not have them until 8.0.<br />
*Informix "CURRENT" operator vs MySQL NOW() function.<br />
*Informix &lt;database&gt;<font color="red"><b>:</b></font>&lt;table&gt;...MySQL &lt;database&gt;<font color="red"><b>.</b></font>&lt;table&gt;<br />
<br />
<br />
What are the differences between SQL statements with Informix and MySQL?&nbsp;&nbsp;(<font color="green">positive</font>/<font color="red">negative</font>/<font color="orange">neutral</font>)<br />
<table><br />
<tr><br />
<td><br />
Informix<br />
</td><br />
<td><br />
MySQL<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
<font color="orange"><b>database</b></font> database;<br />
</td><br />
<td><br />
<font color="orange"><b>use</b></font> database;<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
comments are: "<font color="orange"><b>{</b></font>" comment(s) "<font color="orange"><b>}</b></font>" or "<font color="orange"><b>--</b></font>"<br />
</td><br />
<td><br />
coments are: "<font color="orange"><b>/*</b></font>" comment(s) "<font color="orange"><b>*/</b></font>" or "<font color="orange"><b>--</b></font>"<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
<font color="red">A table NEEDS to be included in ALL select statements</font><br />
</td><br />
<td><br />
<font color="green">A table DOES NOT NEED to be included in select statements</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green"><b>MATCHES</b></font> <i><b>'regular_expr'</b></i> FROM <i><b>table</b></i><br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="red"><b>REGEXP</b></font> <i><b>'regular_expr'</b></i><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green"><b>||</b></font> <i><b>'select_expr'</b></i> FROM <i><b>table</b></i><br />
</td><br />
<td><br />
SELECT <font color="red">CONCAT(</font> <i><b>'select_expr'</b></i>, <i><b>'select_expr'</b></i> <font color="red">)</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <font color="red">FIRST i</font> <i><b>'select_expr'</b></i> FROM <i><b>table</b></i><br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green">LIMIT i</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> FROM <font color="red"><i><b>table</b></i> WHERE 1 = 1</font><br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green">WHERE 1</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr<font color="green">[i,j]</font>'</b></i> FROM <i><b>table</b></i> 1 = 1<br />
</td><br />
<td><br />
SELECT <font color="red">SUBSTR(</font> <i><b>'select_expr', <font color="red">i, j )</font> </b></i>WHERE 1<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <font color="red">CURRENT</font> FROM <i><b>systables</b></i> WHERE <i><b>tabid = 1</b></i><br />
</td><br />
<td><br />
SELECT <font color="green">NOW( )</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT * FROM <i><b>database</b></i><font color="orange"><b>:</b></font><i><b>table</b></i><br />
</td><br />
<td><br />
SELECT * FROM <i><b>database</b></i><font color="orange"><b>.</b></font><i><b>table</b></i><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>database</b></i>:systables.tabname, <i><b>database</b></i>:syscolumns.*<br />
FROM <i><b>database</b></i>:systables<br />
JOIN <i><b>database</b></i>:syscolumns<br />
ON <i><b>database</b></i>:systables.tabid = <i><b>database</b></i>:syscolumns.tabid<br />
WHERE <i><b>database</b></i>:systables.tabname = '<i><b>table</b></i>';<br />
</td><br />
<td><br />
SELECT * FROM information_schema.columns WHERE table_schema = '<i><b>database</b></i>' AND table_name = '<i><b>table</b></i>';<br />
<font color="red"><b>OR</b></font><br />
DESCRIBE <i><b>database</b></i>.<i><b>table</b></i>;<br />
</td><br />
</tr><br />
</table><br />
<br />
<br />
[https://www.ibm.com/developerworks/data/library/techarticle/dm-0801doe/ Compare the Informix Version 12 editions]</div>Kemikohttps://wiki.kemiko.us/index.php?title=Informix&diff=398Informix2017-10-21T18:10:44Z<p>Kemiko: </p>
<hr />
<div>[https://en.wikipedia.org/wiki/IBM_Informix IBM Informix]<br />
<br />
This wiki article says, "Informix is generally considered to be optimized for environments with very low or no database administration, including use as an embedded database. It has a long track record of supporting very high transaction rates and providing uptime characteristics needed for mission critical applications such as manufacturing lines and reservation systems. Informix has been widely deployed in the retail sector, where the low administration overhead makes it useful for in-store deployments."<br />
<br />
<br />
I have worked with Informix in a very large reservation system, insurance and manufacturing. I find the above statement very true.<br />
<br />
<br />
I am currently working with <font color="red"><b>Informix 9.40.FC7</b></font> on HP-UX 11.11 as mostly an adminisrator not a developer. I recently added an <font color="red"><b>Informix 12.10.FC7WE</b></font> replicated server on RHEL 7.3. I started with <font color="red"><b>MySQL 3.23</b></font> on Linux and <font color="red"><b>Informix C-ISAM</b></font> on DEC Ultrix.<br />
<br />
*onstat commands are predefined queries that pull from the shared memory, sysmaster database, system files, etc.&nbsp;&nbsp;They are not output in the best format for reading or joining with other data...so use the sysmaster database to create your own reports with SQL joins&nbsp;&nbsp;([[Informix Monitoring]])<br />
*Learn the sysmaster database...this database holds configurations and statistics<br />
*ESQL/C is very fast for accessing the database. I used it to create session monitoring tool (itop) which is like *nix "top" or MySQL "mytop"<br />
*dbacces (output is vertical if width if greater than 80 characters) and isql are horrible SQL clients...use something like open source [http://squirrel-sql.sourceforge.net/ SQuirreL] for most queries. But, if you want to query table between Informix servers you have to use Informix tools like dbacces and isql.<br />
*Every database has catalog tables that hold table, column, index information, etc. (select tabname from systables where tabid < 100;)<br />
*Find columns with SQL...SELECT tabname, syscolumns.* FROM systables, syscolumns WHERE systables.tabid = syscolumns.tabid AND tabname = 'table'; or with ANSI join SELECT t.tabname, c.* FROM systables t JOIN syscolumns c ON t.tabid = c.tabid;<br />
*Raw devices are faster which Informix uses very well<br />
*Optimize your statistics plan for better performance<br />
*HPL (High Performance Loader) is a very awkward GUI tool, but can unload and reload tables quicker using a raw data format<br />
*Create enough space for logical logging to prevent downtime if the tape fails. The engine will block transaction if these logs can't be backed up<br />
*Large tables can really slow down OLTP databases. So, archive tables that are OLTP.<br />
*A "dummy" archive, ontape -s -L 0...w/TAPEDEV set to /dev/null (in onconfig), must be done after some configuration changes<br />
*Our Informix 9.40.FC7, which is 64 bit, has a 2GiB file limitation writing to HP-UX 11.11's file system...not the actual database data files going to a tape or pipe. So 9.40 can not archive a large database to disk without going to tape or through a pipe. 12.10 does not have this issue.<br />
*The system log only stamps the log with the date when the first record of the day is written...then only a time stamp is on the records.&nbsp;&nbsp;In 12.10 set "MSG_DATE 1" in the onconfig file to get the date stamp on each record.<br />
*Try and size your initial extents large enough that the engine does not have to keep creating more extents. Multiple extents fragment your table spaces.<br />
*Informix date and time fields/functions are very different from MySQL<br />
*I really like some of Informix's SQL extensions...like "||" for concatenation, field[n,m] for substring, field matches( regexp ), first, etc.<br />
*Don't hit ctrl-c while starting the database (command oninit)...this will leave share memory in limbo<br />
*Informix can do queries between 2 servers.&nbsp;&nbsp;Use lowercase strings for DBSERVERNAME and DBSERVERALIASES values<br />
*Do not OS "nice" dbaccess, etc. The engine handles the priority. Set MAX_PDQPRIORITY (Parallel Database Query) to process queries faster.<br />
*Informix is closely tied to the OS. Users and passwords are created and maintained by the OS.<br />
*Informix privileges are definitely different from MySQL. Informix has a "connect" grant that I like because it is the only privilges you need to revoke to deny a user access make other grants void! Also, Informix can list "all" grants in one statement...MySQL can not!<br />
*<font color="red">Informix 12.10 has a single user mode...does MySQL? (read_only=1)</font><br />
*Informix has had descending btree indexes since 9.40, but MySQL will not have them until 8.0.<br />
*Informix "CURRENT" operator vs MySQL NOW() function.<br />
*Informix &lt;database&gt;<font color="red"><b>:</b></font>&lt;table&gt;...MySQL &lt;database&gt;<font color="red"><b>.</b></font>&lt;table&gt;<br />
<br />
<br />
What are the differences between SQL statements with Informix and MySQL?&nbsp;&nbsp;(<font color="green">positive</font>/<font color="red">negative</font>/<font color="orange">neutral</font>)<br />
<table><br />
<tr><br />
<td><br />
Informix<br />
</td><br />
<td><br />
MySQL<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
database <database to use>;<br />
</td><br />
<td><br />
use <database to use>;<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
comments are: "<font color="orange"><b>{</b></font>" comment(s) "<font color="orange"><b>}</b></font>" or "<font color="orange"><b>--</b></font>"<br />
</td><br />
<td><br />
coments are: "<font color="orange"><b>/*</b></font>" comment(s) "<font color="orange"><b>*/</b></font>" or "<font color="orange"><b>--</b></font>"<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
<font color="red">A table NEEDS to be included in ALL select statements</font><br />
</td><br />
<td><br />
<font color="green">A table DOES NOT NEED to be included in select statements</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green"><b>MATCHES</b></font> <i><b>'regular_expr'</b></i> FROM <i><b>table</b></i><br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="red"><b>REGEXP</b></font> <i><b>'regular_expr'</b></i><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green"><b>||</b></font> <i><b>'select_expr'</b></i> FROM <i><b>table</b></i><br />
</td><br />
<td><br />
SELECT <font color="red">CONCAT(</font> <i><b>'select_expr'</b></i>, <i><b>'select_expr'</b></i> <font color="red">)</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <font color="red">FIRST i</font> <i><b>'select_expr'</b></i> FROM <i><b>table</b></i><br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green">LIMIT i</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> FROM <font color="red"><i><b>table</b></i> WHERE 1 = 1</font><br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green">WHERE 1</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr<font color="green">[i,j]</font>'</b></i> FROM <i><b>table</b></i> 1 = 1<br />
</td><br />
<td><br />
SELECT <font color="red">SUBSTR(</font> <i><b>'select_expr', <font color="red">i, j )</font> </b></i>WHERE 1<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <font color="red">CURRENT</font> FROM <i><b>systables</b></i> WHERE tabid = 1<br />
</td><br />
<td><br />
SELECT <font color="green">NOW( )</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT * FROM &lt;database&gt;<font color="orange"><b>:</b></font>&lt;table&gt;<br />
</td><br />
<td><br />
SELECT * FROM &lt;database&gt;<font color="orange"><b>.</b></font>&lt;table&gt;<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT systables.tabname, syscolumns.*<br />
FROM systables<br />
JOIN syscolumns<br />
ON systables.tabid = syscolumns.tabid<br />
WHERE tabname = 'table';<br />
</td><br />
<td><br />
SELECT * FROM information_schema.columns WHERE table_schema = 'database' and table_name = 'table';<br />
<font color="red"><b>OR</b></font><br />
DESCRIBE table;<br />
</td><br />
</tr><br />
</table><br />
<br />
<br />
[https://www.ibm.com/developerworks/data/library/techarticle/dm-0801doe/ Compare the Informix Version 12 editions]</div>Kemikohttps://wiki.kemiko.us/index.php?title=Informix&diff=397Informix2017-10-21T16:37:12Z<p>Kemiko: </p>
<hr />
<div>[https://en.wikipedia.org/wiki/IBM_Informix IBM Informix]<br />
<br />
This wiki article says, "Informix is generally considered to be optimized for environments with very low or no database administration, including use as an embedded database. It has a long track record of supporting very high transaction rates and providing uptime characteristics needed for mission critical applications such as manufacturing lines and reservation systems. Informix has been widely deployed in the retail sector, where the low administration overhead makes it useful for in-store deployments."<br />
<br />
<br />
I have worked with Informix in a very large reservation system, insurance and manufacturing. I find the above statement very true.<br />
<br />
<br />
I am currently working with <font color="red"><b>Informix 9.40.FC7</b></font> on HP-UX 11.11 as mostly an adminisrator not a developer. I recently added an <font color="red"><b>Informix 12.10.FC7WE</b></font> replicated server on RHEL 7.3. I started with <font color="red"><b>MySQL 3.23</b></font> on Linux and <font color="red"><b>Informix C-ISAM</b></font> on DEC Ultrix.<br />
<br />
*onstat commands are predefined queries that pull from the shared memory, sysmaster database, system files, etc.&nbsp;&nbsp;They are not output in the best format for reading or joining with other data...so use the sysmaster database to create your own reports with SQL joins&nbsp;&nbsp;([[Informix Monitoring]])<br />
*Learn the sysmaster database...this database holds configurations and statistics<br />
*ESQL/C is very fast for accessing the database. I used it to create session monitoring tool (itop) which is like *nix "top" or MySQL "mytop"<br />
*dbacces (output is vertical if width if greater than 80 characters) and isql are horrible SQL clients...use something like open source [http://squirrel-sql.sourceforge.net/ SQuirreL] for most queries. But, if you want to query table between Informix servers you have to use Informix tools like dbacces and isql.<br />
*Every database has catalog tables that hold table, column, index information, etc. (select tabname from systables where tabid < 100;)<br />
*Find columns with SQL...SELECT tabname, syscolumns.* FROM systables, syscolumns WHERE systables.tabid = syscolumns.tabid AND tabname = 'table'; or with ANSI join SELECT t.tabname, c.* FROM systables t JOIN syscolumns c ON t.tabid = c.tabid;<br />
*Raw devices are faster<br />
*Optimize your statistics plan<br />
*HPL (High Performance Loader) is a very awkward GUI tool, but can unload and reload tables quicker using a raw data format<br />
*Create enough space for logical logging to prevent downtime if the tape fails. The engine will stop running if these logs can't be backed up<br />
*Large tables can really slow down OLTP databases<br />
*A "dummy" archive, ontape -s -L 0...w/TAPEDEV set to /dev/null (in onconfig), must be done after some configuration changes<br />
*Our Informix 9.40.FC7, which is 64 bit, has a 2GiB file limitation writing to HP-UX 11.11's file system...not the actual database data files going to a tape or pipe. So 9.40 can not archive a large database to disk without going through a pipe. 12.10 does not have this issue.<br />
*The system log only stamps the log with the date when the first record of the day is written...then only a time stamp is on the records.&nbsp;&nbsp;In 12.10 set "MSG_DATE 1" in the onconfig file.<br />
*Try and size your initial extents large enough that table spaces do not have a lot of additional extents (a physical unit of storage)<br />
*Informix date and time fields/functions are very different from MySQL<br />
*I really like some of Informix's SQL extensions...like "||" for concatenation, field[n,m] for substring, field matches( regexp ), etc.<br />
*Don't hit ctrl-c while starting the database (command oninit)...this will leave share memory in limbo<br />
*Informix can do queries between 2 servers.&nbsp;&nbsp;Use lowercase strings to configure DBSERVERNAME and DBSERVERALIASES<br />
*Do not "nice" dbaccess, etc. The engine handles the priority. Set MAX_PDQPRIORITY (Parallel Database Query) to process queries faster.<br />
*Informix is closely tied to the OS. Users and passwords are created and maintained by the OS.<br />
*Informix privileges are definitely different from MySQL. Informix has a "connect" grant that I like because it is the only privilges you need to revoke to deny a user access! Also, Informix can list "all" grants in one statement...MySQL can not!<br />
*<font color="red">Informix 12.10 has a single user mode...does MySQL? (read_only=1)</font><br />
*Informix has had descending btree indexes since 9.40, but MySQL will not have them until 8.0.<br />
*Informix "CURRENT" operator vs MySQL NOW() function.<br />
*Informix &lt;database&gt;<font color="red"><b>:</b></font>&lt;table&gt;...MySQL &lt;database&gt;<font color="red"><b>.</b></font>&lt;table&gt;<br />
<br />
<br />
What are the differences between SQL statements with Informix and MySQL?&nbsp;&nbsp;(<font color="green">positive</font>/<font color="red">negative</font>/<font color="orange">neutral</font>)<br />
<table><br />
<tr><br />
<td><br />
Informix<br />
</td><br />
<td><br />
MySQL<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
database <database to use>;<br />
</td><br />
<td><br />
use <database to use>;<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
comments are: "<font color="orange"><b>{</b></font>" comment(s) "<font color="orange"><b>}</b></font>" or "<font color="orange"><b>--</b></font>"<br />
</td><br />
<td><br />
coments are: "<font color="orange"><b>/*</b></font>" comment(s) "<font color="orange"><b>*/</b></font>" or "<font color="orange"><b>--</b></font>"<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
<font color="red">A table NEEDS to be included in ALL select statements</font><br />
</td><br />
<td><br />
<font color="green">A table DOES NOT NEED to be included in select statements</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green"><b>MATCHES</b></font> <i><b>'regular_expr'</b></i> FROM <i><b>table</b></i><br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="red"><b>REGEXP</b></font> <i><b>'regular_expr'</b></i><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green"><b>||</b></font> <i><b>'select_expr'</b></i> FROM <i><b>table</b></i><br />
</td><br />
<td><br />
SELECT <font color="red">CONCAT(</font> <i><b>'select_expr'</b></i>, <i><b>'select_expr'</b></i> <font color="red">)</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <font color="red">FIRST i</font> <i><b>'select_expr'</b></i> FROM <i><b>table</b></i><br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green">LIMIT i</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> FROM <font color="red"><i><b>table</b></i> WHERE 1 = 1</font><br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green">WHERE 1</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr<font color="green">[i,j]</font>'</b></i> FROM <i><b>table</b></i> 1 = 1<br />
</td><br />
<td><br />
SELECT <font color="red">SUBSTR(</font> <i><b>'select_expr', <font color="red">i, j )</font> </b></i>WHERE 1<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <font color="red">CURRENT</font> FROM <i><b>systables</b></i> WHERE tabid = 1<br />
</td><br />
<td><br />
SELECT <font color="green">NOW( )</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <database>:systables.tabname, <database>:syscolumns.*<br />
FROM <database>:systables, <database>:syscolumns<br />
WHERE <database>:systables.tabid = <database>:syscolumns.tabid and <database>:systables.tabid > 100<br />
</td><br />
<td><br />
SELECT * FROM information_schema.columns WHERE table_schema = '<database>'; or DESCRIBE table<br />
</td><br />
</tr><br />
</table><br />
<br />
<br />
[https://www.ibm.com/developerworks/data/library/techarticle/dm-0801doe/ Compare the Informix Version 12 editions]</div>Kemikohttps://wiki.kemiko.us/index.php?title=Informix&diff=396Informix2017-10-20T15:45:26Z<p>Kemiko: </p>
<hr />
<div>[https://en.wikipedia.org/wiki/IBM_Informix IBM Informix]<br />
<br />
This wiki article says, "Informix is generally considered to be optimized for environments with very low or no database administration, including use as an embedded database. It has a long track record of supporting very high transaction rates and providing uptime characteristics needed for mission critical applications such as manufacturing lines and reservation systems. Informix has been widely deployed in the retail sector, where the low administration overhead makes it useful for in-store deployments."<br />
<br />
<br />
I have worked with Informix in both manufacturing and reservations and find this to be true.<br />
<br />
<br />
I am currently working with <font color="red"><b>Informix 9.40.FC7 on HP-UX 11.11</b></font> as an adminisrator not a developer. We finally installed a new version of Informix...<font color="red"><b>12.10.FC7WE on RHEL 7.3</b></font>. However, I started with <font color="red"><b>MySQL and Informix C-ISAM on Linux</b></font>.<br />
<br />
*onstat commands are predefined queries that pull from the shared memory, sysmaster database, system files, etc.&nbsp;&nbsp;They are not output in the best format for reading or joining with other data...so use the sysmaster database to create your own reports with SQL joins&nbsp;&nbsp;([[Informix Monitoring]])<br />
*Learn the sysmaster database...this database holds configurations and statistics<br />
*ESQL/C is very fast for accessing the database (itop)<br />
*dbacces (output is vertical if width if greater than 80 characters) and isql are horrible SQL clients...use something like open source [http://squirrel-sql.sourceforge.net/ SQuirreL]<br />
*Every database has catalog tables that hold table, column, index information, etc. (select tabname from systables where tabid < 100;)<br />
*Find columns with SQL...select tabname, syscolumns.* from systables, syscolumns where systables.tabid = syscolumns.tabid and tabname = 'table';<br />
*Raw devices are faster<br />
*Optimize your statistics plan<br />
*HPL (High Performance Loader) is a very awkward GUI tool, but can unload and reload tables quicker using a raw data format<br />
*Create enough space for logical logging to prevent downtime if the tape fails. The engine will stop running if these logs can't be backed up<br />
*Large tables can really slow down OLTP databases<br />
*A "dummy" archive, ontape -s -L 0...w/TAPEDEV set to /dev/null (in onconfig), must be done after some configuration changes<br />
*Our Informix 9.40.FC7, which is 64 bit, has a 2GiB file limitation writing to HP-UX 11.11's file system...not the actual database data files going to a tape or pipe. So 9.40 can not archive a large database to disk without going through a pipe. 12.10 does not have this issue.<br />
*The system log only stamps the log with the date when the first record of the day is written...then only a time stamp is on the records.&nbsp;&nbsp;In 12.10 set "MSG_DATE 1" in the onconfig file.<br />
*Try and size your initial extents large enough that table spaces do not have a lot of additional extents (a physical unit of storage)<br />
*Informix date and time fields/functions are very different from MySQL<br />
*I really like some of Informix's SQL extensions...like "||" for concatenation, field[n,m] for substring, field matches( regexp ), etc.<br />
*Don't hit ctrl-c while starting the database (command oninit)...this will leave share memory in limbo<br />
*Informix can do queries between 2 servers.&nbsp;&nbsp;Use lowercase strings to configure DBSERVERNAME and DBSERVERALIASES<br />
*Do not "nice" dbaccess, etc. The engine handles the priority. Set MAX_PDQPRIORITY (Parallel Database Query) to process queries faster.<br />
*Informix is closely tied to the OS. Users and passwords are created and maintained by the OS.<br />
*Informix privileges are definitely different from MySQL. Informix has a "connect" grant that I like because it is the only privilges you need to revoke to deny a user access! Also, Informix can list "all" grants in one statement...MySQL can not!<br />
*<font color="red">Informix 12.10 has a single user mode...does MySQL? (read_only=1)</font><br />
*Informix has had descending btree indexes since 9.40, but MySQL will not have them until 8.0.<br />
*Informix "CURRENT" operator vs MySQL NOW() function.<br />
*Informix &lt;database&gt;<font color="red"><b>:</b></font>&lt;table&gt;...MySQL &lt;database&gt;<font color="red"><b>.</b></font>&lt;table&gt;<br />
<br />
<br />
What are the differences between SQL statements with Informix and MySQL?&nbsp;&nbsp;(<font color="green">positive</font>/<font color="red">negative</font>/<font color="orange">neutral</font>)<br />
<table><br />
<tr><br />
<td><br />
Informix<br />
</td><br />
<td><br />
MySQL<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
database <database to use>;<br />
</td><br />
<td><br />
use <database to use>;<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
comments are: "<font color="orange"><b>{</b></font>" comment(s) "<font color="orange"><b>}</b></font>" or "<font color="orange"><b>--</b></font>"<br />
</td><br />
<td><br />
coments are: "<font color="orange"><b>/*</b></font>" comment(s) "<font color="orange"><b>*/</b></font>" or "<font color="orange"><b>--</b></font>"<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
<font color="red">A table NEEDS to be included in ALL select statements</font><br />
</td><br />
<td><br />
<font color="green">A table DOES NOT NEED to be included in select statements</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green"><b>MATCHES</b></font> <i><b>'regular_expr'</b></i> FROM <i><b>table</b></i><br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="red"><b>REGEXP</b></font> <i><b>'regular_expr'</b></i><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green"><b>||</b></font> <i><b>'select_expr'</b></i> FROM <i><b>table</b></i><br />
</td><br />
<td><br />
SELECT <font color="red">CONCAT(</font> <i><b>'select_expr'</b></i>, <i><b>'select_expr'</b></i> <font color="red">)</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <font color="red">FIRST i</font> <i><b>'select_expr'</b></i> FROM <i><b>table</b></i><br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green">LIMIT i</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> FROM <font color="red"><i><b>table</b></i> WHERE 1 = 1</font><br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green">WHERE 1</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr<font color="green">[i,j]</font>'</b></i> FROM <i><b>table</b></i> 1 = 1<br />
</td><br />
<td><br />
SELECT <font color="red">SUBSTR(</font> <i><b>'select_expr', <font color="red">i, j )</font> </b></i>WHERE 1<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <font color="red">CURRENT</font> FROM <i><b>systables</b></i> WHERE tabid = 1<br />
</td><br />
<td><br />
SELECT <font color="green">NOW( )</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <database>:systables.tabname, <database>:syscolumns.*<br />
FROM <database>:systables, <database>:syscolumns<br />
WHERE <database>:systables.tabid = <database>:syscolumns.tabid and <database>:systables.tabid > 100<br />
</td><br />
<td><br />
SELECT * FROM information_schema.columns WHERE table_schema = '<database>'; or DESCRIBE table<br />
</td><br />
</tr><br />
</table><br />
<br />
<br />
[https://www.ibm.com/developerworks/data/library/techarticle/dm-0801doe/ Compare the Informix Version 12 editions]</div>Kemikohttps://wiki.kemiko.us/index.php?title=Informix&diff=395Informix2017-10-20T13:59:34Z<p>Kemiko: </p>
<hr />
<div>[https://en.wikipedia.org/wiki/IBM_Informix IBM Informix]<br />
<br />
This wiki article says, "Informix is generally considered to be optimized for environments with very low or no database administration, including use as an embedded database. It has a long track record of supporting very high transaction rates and providing uptime characteristics needed for mission critical applications such as manufacturing lines and reservation systems. Informix has been widely deployed in the retail sector, where the low administration overhead makes it useful for in-store deployments."<br />
<br />
<br />
I have worked with Informix in both manufacturing and reservations and find this to be true.<br />
<br />
<br />
I am currently working with <font color="red"><b>Informix 9.40.FC7 on HP-UX 11.11</b></font> as an adminisrator not a developer. We finally installed a new version of Informix...<font color="red"><b>12.10.FC7WE on RHEL 7.3</b></font>. However, I started with <font color="red"><b>MySQL and Informix C-ISAM on Linux</b></font>.<br />
<br />
*onstat commands are predefined queries that pull from the shared memory, sysmaster database, system files, etc.&nbsp;&nbsp;They are not output in the best format for reading or joining with other data...so use the sysmaster database to create your own reports with SQL joins&nbsp;&nbsp;([[Informix Monitoring]])<br />
*Learn the sysmaster database...this database holds configurations and statistics<br />
*ESQL/C is very fast for accessing the database (itop)<br />
*dbacces (output is vertical if width if greater than 80 characters) and isql are horrible SQL clients...use something like open source [http://squirrel-sql.sourceforge.net/ SQuirreL]<br />
*Every database has catalog tables that hold table, column, index information, etc. (select tabname from systables where tabid < 100;)<br />
*Find columns with SQL...select tabname, syscolumns.* from systables, syscolumns where systables.tabid = syscolumns.tabid and tabname = 'table';<br />
*Raw devices are faster<br />
*Optimize your statistics plan<br />
*HPL (High Performance Loader) is a very awkward GUI tool, but can unload and reload tables quicker using a raw data format<br />
*Create enough space for logical logging to prevent downtime if the tape fails. The engine will stop running if these logs can't be backed up<br />
*Large tables can really slow down OLTP databases<br />
*A "dummy" archive, ontape -s -L 0...w/TAPEDEV set to /dev/null (in onconfig), must be done after some configuration changes<br />
*Our Informix 9.40.FC7, which is 64 bit, has a 2GiB file limitation writing to HP-UX 11.11's file system...not the actual database data files going to a tape or pipe. So 9.40 can not archive a large database to disk without going through a pipe. 12.10 does not have this issue.<br />
*The system log only stamps the log with the date when the first record of the day is written...then only a time stamp is on the records.&nbsp;&nbsp;In 12.10 set "MSG_DATE 1" in the onconfig file.<br />
*Try and size your initial extents large enough that table spaces do not have a lot of additional extents (a physical unit of storage)<br />
*Informix date and time fields/functions are very different from MySQL<br />
*I really like some of Informix's SQL extensions...like "||" for concatenation, field[n,m] for substring, field matches( regexp ), etc.<br />
*Don't hit ctrl-c while starting the database (command oninit)...this will leave share memory in limbo<br />
*With Informix it is really easy to setup doing queries with two separate servers!<br />
*Do not "nice" dbaccess, etc. The engine handles the priority. Set MAX_PDQPRIORITY (Parallel Database Query) to process queries faster.<br />
*Informix is closely tied to the OS. Users and passwords are created and maintained by the OS.<br />
*Informix privileges are definitely different from MySQL. Informix has a "connect" grant that I like because it is the only privilges you need to revoke to deny a user access! Also, Informix can list "all" grants in one statement...MySQL can not!<br />
*<font color="red">Informix 12.10 has a single user mode...does MySQL? (read_only=1)</font><br />
*Informix has had descending btree indexes since 9.40, but MySQL will not have them until 8.0.<br />
*Informix "CURRENT" operator vs MySQL NOW() function.<br />
*Informix &lt;database&gt;<font color="red"><b>:</b></font>&lt;table&gt;...MySQL &lt;database&gt;<font color="red"><b>.</b></font>&lt;table&gt;<br />
<br />
<br />
What are the differences between SQL statements with Informix and MySQL?&nbsp;&nbsp;(<font color="green">positive</font>/<font color="red">negative</font>/<font color="orange">neutral</font>)<br />
<table><br />
<tr><br />
<td><br />
Informix<br />
</td><br />
<td><br />
MySQL<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
database <database to use>;<br />
</td><br />
<td><br />
use <database to use>;<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
comments are: "<font color="orange"><b>{</b></font>" comment(s) "<font color="orange"><b>}</b></font>" or "<font color="orange"><b>--</b></font>"<br />
</td><br />
<td><br />
coments are: "<font color="orange"><b>/*</b></font>" comment(s) "<font color="orange"><b>*/</b></font>" or "<font color="orange"><b>--</b></font>"<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
<font color="red">A table NEEDS to be included in ALL select statements</font><br />
</td><br />
<td><br />
<font color="green">A table DOES NOT NEED to be included in select statements</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green"><b>MATCHES</b></font> <i><b>'regular_expr'</b></i> FROM <i><b>table</b></i><br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="red"><b>REGEXP</b></font> <i><b>'regular_expr'</b></i><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green"><b>||</b></font> <i><b>'select_expr'</b></i> FROM <i><b>table</b></i><br />
</td><br />
<td><br />
SELECT <font color="red">CONCAT(</font> <i><b>'select_expr'</b></i>, <i><b>'select_expr'</b></i> <font color="red">)</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <font color="red">FIRST i</font> <i><b>'select_expr'</b></i> FROM <i><b>table</b></i><br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green">LIMIT i</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> FROM <font color="red"><i><b>table</b></i> WHERE 1 = 1</font><br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green">WHERE 1</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr<font color="green">[i,j]</font>'</b></i> FROM <i><b>table</b></i> 1 = 1<br />
</td><br />
<td><br />
SELECT <font color="red">SUBSTR(</font> <i><b>'select_expr', <font color="red">i, j )</font> </b></i>WHERE 1<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <font color="red">CURRENT</font> FROM <i><b>systables</b></i> WHERE tabid = 1<br />
</td><br />
<td><br />
SELECT <font color="green">NOW( )</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <database>:systables.tabname, <database>:syscolumns.*<br />
FROM <database>:systables, <database>:syscolumns<br />
WHERE <database>:systables.tabid = <database>:syscolumns.tabid and <database>:systables.tabid > 100<br />
</td><br />
<td><br />
SELECT * FROM information_schema.columns WHERE table_schema = '<database>'; or DESCRIBE table<br />
</td><br />
</tr><br />
</table><br />
<br />
<br />
[https://www.ibm.com/developerworks/data/library/techarticle/dm-0801doe/ Compare the Informix Version 12 editions]</div>Kemikohttps://wiki.kemiko.us/index.php?title=Tech_Tips&diff=394Tech Tips2017-10-15T17:59:57Z<p>Kemiko: </p>
<hr />
<div>'''Trouble Shooting''':<br />
<br />
<ul><br />
<li><br />
Start with the basics...like power, network, etc.<br />
</li><br />
</ul><br />
<br />
'''General''':<br />
<br />
<ul><br />
<li><br />
Know the animal before trying to tame.<br />
</li><br />
<li><br />
Some vendors use MB/GB (decimal...in goups of 1000) and some use MiB/GiB (binary...in groups of 1024).<br />
</li><br />
<li><br />
Always query before running modification command(s) whether using the OS, database or apps.<br />
</li><br />
<li><br />
Backup or already have a backup before modifying files, database, apps.<br />
</li><br />
<li><br />
Learn your editor(s) well...its functionality can save a ton of time<br />
</li><br />
<li><br />
Learn all available debugging tool...it can save a ton of time<br />
</li><br />
<li><br />
Always use logging<br />
<ul><br />
<li><br />
Check logs often or write smart alerts that scan logs<br />
</li><br />
<li><br />
Rotate logs to keep them manageable<br />
</li><br />
<li><br />
tail -f error logs when developing<br />
</li><br />
<li><br />
Good pairing words: staring/finished, source/target, etc.<br />
</li><br />
</ul><br />
</li><br />
<li><br />
Always learn the background workings. That means learn and use the command line and script NOT just the GUI tools<br />
</li><br />
<li><br />
Always check your work! Even when making a simply change...if done wrong can cause large issues.<br />
</li><br />
<li><br />
Automate tasks. Automating tasks take a very good understanding of the software and intended goal.<br />
</li><br />
</ul><br />
<br />
'''Development''':<br />
<ul><br />
<li><br />
Naming<br />
<ul><br />
<li><br />
Avoid spaces.<br />
</li><br />
<li><br />
Use camelCase.<br />
</li><br />
<li><br />
Name common items with the common word starting each item.<br />
</li><br />
<li><br />
Name same item, but numbered with enough padding to sort correctly. ex: if going to at least 10 use 01-10 instead of 1-10.<br />
</li><br />
<li><br />
Name date by number not name and most general to specific. So they sort correctly. ex: 20161231 instead of Dec31-2016, etc.<br />
</li><br />
<li><br />
Name using noun first then verb. ex: logCreate, logList, dateStart, dateEnd, etc.<br />
</li><br />
</ul><br />
</li><br />
</ul><br />
<br />
<ul><br />
<li><br />
Coding<br />
<ul><br />
<li><br />
Top-down vs bottom-up design<br />
</li><br />
<li><br />
Always add comments...you may not remember what you did days, months, years from now<br />
</li><br />
<li><br />
Line block brackets up vertically<br />
</li><br />
<li><br />
Happy balance between elegance/complexity and readability/maintainability<br />
</li><br />
<li><br />
Happy balance between too long and too short variable naming<br />
</li><br />
<li><br />
Pick a style and stay consistent...this sometime means following someone else's style when modifying existing code<br />
</li><br />
<li><br />
Learn your debugging tool(s)...they can save a ton of time<br />
</li><br />
<li><br />
Give some thought to designing your log files...<br />
<ul><br />
<li><br />
Put the date and time in each record<br />
</li><br />
<li><br />
Format well...XML, JSON, delimited, etc.<br />
</li><br />
<li><br />
Make sure enough data is included to be helpful<br />
</li><br />
</ul><br />
</li><br />
</ul><br />
</li><br />
</ul><br />
<br />
'''*nix''':<br />
<br />
<ul><br />
<li><br />
Type "env" and/or "set" in the shell to display all the environment variables<br />
</li><br />
<li><br />
Use "set -x" to debug shell scripts ("set +x" turns debugging off)<br />
</li><br />
<li><br />
Use "set -o vi" to use vi to navigate/modify shell commands ("set +o" turns vi off)<br />
</li><br />
<li><br />
crontab<br />
<ul><br />
<li><br />
Put number in 09 format to make easier to read, parse and sort (multiple spaces are fine...fields are space delimited)<br />
</li><br />
<li><br />
Always redirect command output somewhere, log file, /dev/null, etc.&nbsp;&nbsp;Otherwise output will be sent to the user's email<br />
</li><br />
<li><br />
Command must be one line.&nbsp;&nbsp;Semicolons are okay to execute mulitple commands<br />
</li><br />
<li><br />
The modulus operator can be used to run commands. "*/5" in the minute field will run the command every 5 minutes<br />
</li><br />
</ul><br />
</li><br />
</ul><br />
<br />
<br />
'''SQL''':<br />
<br />
<ul><br />
<li><br />
In general use a where clause even if selecting everything..."where 1" or "where 1 = 1". This reminds someone editing the code that this query is operating on EVERYTHING. Remove the where clause can sometimes greatly optimize code. Make a comment to note there is NO where clause.<br />
</li><br />
<li><br />
Comments are handy even in SQL for debugging and understanding. "--comments" is universal, but also /* comments */ in MySQL, {comments} in Informix, etc.<br />
</li><br />
<li><br />
Always comment out a drop statement right after executing, so it is not accidentally run again<br />
</li><br />
<li><br />
Indexes are very important to the performance of a database<br />
</li><br />
<ul></div>Kemikohttps://wiki.kemiko.us/index.php?title=Tech_Tips&diff=393Tech Tips2017-10-15T17:58:16Z<p>Kemiko: </p>
<hr />
<div>'''Trouble Shooting''':<br />
<br />
<ul><br />
<li><br />
Start with the basics...like power, network, etc.<br />
</li><br />
</ul><br />
<br />
'''General''':<br />
<br />
<ul><br />
<li><br />
Know the animal before trying to tame.<br />
</li><br />
<li><br />
Some vendors use MB/GB (decimal...in goups of 1000) and some use MiB/GiB (binary...in groups of 1024).<br />
</li><br />
<li><br />
Always query before running modification command(s) whether using the OS, database or apps.<br />
</li><br />
<li><br />
Backup or already have a backup before modifying files, database, apps.<br />
</li><br />
<li><br />
Learn your editor(s) well...its functionality can save a ton of time<br />
</li><br />
<li><br />
Learn all available debugging tool...it can save a ton of time<br />
</li><br />
<li><br />
Always use logging<br />
<ul><br />
<li><br />
Check logs often or write smart alerts that scan logs<br />
</li><br />
<li><br />
Rotate logs to keep them manageable<br />
</li><br />
<li><br />
tail -f error logs when developing<br />
</li><br />
<li><br />
Good pairing words: staring/finished, source/target, etc.<br />
</li><br />
</ul><br />
</li><br />
<li><br />
Always learn the background workings. That means learn and use the command line and script NOT just the GUI tools<br />
</li><br />
<li><br />
Always check your work! Even when making a simply change...if done wrong can cause large issues.<br />
</li><br />
<li><br />
Automate tasks. Automating tasks take a very good understanding of the software and intended goal.<br />
</li><br />
</ul><br />
<br />
'''Development''':<br />
<ul><br />
<li><br />
Naming<br />
<ul><br />
<li><br />
Avoid spaces.<br />
</li><br />
<li><br />
Use camelCase.<br />
</li><br />
<li><br />
Name common items with the common word starting each item.<br />
</li><br />
<li><br />
Name same item, but numbered with enough padding to sort correctly. ex: if going to at least 10 use 01-10 instead of 1-10.<br />
</li><br />
<li><br />
Name date by number not name and most general to specific. So they sort correctly. ex: 20161231 instead of Dec31-2016, etc.<br />
</li><br />
<li><br />
Name using noun first then verb. ex: logCreate, logList, dateStart, dateEnd, etc.<br />
</li><br />
</ul><br />
</li><br />
</ul><br />
<br />
<ul><br />
<li><br />
Coding<br />
<ul><br />
<li><br />
Top-down vs bottom-up design<br />
</li><br />
<li><br />
Always add comments...you may not remember what you did days, months, years from now<br />
</li><br />
<li><br />
Line block brackets up vertically<br />
</li><br />
<li><br />
Happy balance between elegance/complexity and readability/maintainability<br />
</li><br />
<li><br />
Happy balance between too long and too short variable naming<br />
</li><br />
<li><br />
Pick a style and stay consistent...this sometime means following someone else's style when modifying existing code<br />
</li><br />
<li><br />
Learn your debugging tool(s)...they can save a ton of time<br />
</li><br />
<li><br />
Give some thought to designing your log files...<br />
<ul><br />
<li><br />
Put the date and time in each record<br />
</li><br />
<li><br />
Format well...XML, JSON, delimited, etc.<br />
</li><br />
<li><br />
Make sure enough data is included to be helpful<br />
</li><br />
</ul><br />
</li><br />
</ul><br />
</li><br />
</ul><br />
<br />
'''*nix''':<br />
<br />
<ul><br />
<li><br />
Type "env" and/or "set" in the shell to display all the environment variables<br />
</li><br />
<li><br />
Use "set -x" to debug shell scripts ("set +x" turns debugging off)<br />
</li><br />
<li><br />
Use "set -o vi" to use vi to navigate/modify shell commands ("set +o" turns vi off)<br />
</li><br />
<li><br />
crontab<br />
<ul><br />
<li><br />
Put number in 09 format to make easier to read, parse and sort (multiple spaces are fine...fields are space delimited)<br />
</li><br />
<li><br />
Always redirect command output somewhere, log file, /dev/null, etc.&nbsp;&nbsp;Otherwise output will be sent to the user's email<br />
</li><br />
<li><br />
Command must be one line.&nbsp;&nbsp;Semicolons are okay to execute mulitple commands<br />
</li><br />
<li><br />
The modulus operator can be used to run commands. "*/5" in the minute field will run the command every 5 minutes<br />
</li><br />
</ul><br />
</li><br />
</ul><br />
<br />
<br />
'''SQL''':<br />
<br />
<ul><br />
<li><br />
In general use a where clause even if selecting everything..."where 1" or "where 1 = 1". This reminds someone editing the code that this query is operating on EVERYTHING. Remove the where clause can sometimees greatly optimize code. Make a comment to note this.<br />
</li><br />
<li><br />
Comments are handy even in SQL for debugging and understanding. "--comments" is universal, but also /* comments */ in MySQL, {comments} in Informix, etc.<br />
</li><br />
<li><br />
Always comment out a drop statement right after executing, so it is not accidentally run again<br />
</li><br />
<li><br />
Indexes are very important to the performance of a database<br />
</li><br />
<ul></div>Kemikohttps://wiki.kemiko.us/index.php?title=Tech_Tips&diff=392Tech Tips2017-10-15T17:35:13Z<p>Kemiko: </p>
<hr />
<div>'''Trouble Shooting''':<br />
<br />
<ul><br />
<li><br />
Start with the basics...like power, network, etc.<br />
</li><br />
</ul><br />
<br />
'''General''':<br />
<br />
<ul><br />
<li><br />
Know the animal before trying to tame.<br />
</li><br />
<li><br />
Some vendors use MB/GB (decimal...in goups of 1000) and some use MiB/GiB (binary...in groups of 1024).<br />
</li><br />
<li><br />
Always query before running modification command(s) whether using the OS, database or apps.<br />
</li><br />
<li><br />
Backup or already have a backup before modifying files, database, apps.<br />
</li><br />
<li><br />
Learn your editor(s) well...it's functions can save a ton of time<br />
</li><br />
<li><br />
Learn all available debugging tool...it can save a ton of time<br />
</li><br />
<li><br />
Always use logging<br />
<ul><br />
<li><br />
Check logs often or write smart alerts that scan logs<br />
</li><br />
<li><br />
Rotate logs to keep them manageable<br />
</li><br />
<li><br />
tail -f error logs when developing<br />
</li><br />
<li><br />
Good pairing words: staring/finished, source/target, etc.<br />
</li><br />
</ul><br />
</li><br />
<li><br />
Always learn the background workings. That means learn and use the command line and script NOT just the GUI tools<br />
</li><br />
<li><br />
Always check your work! Even when making a simply change...if done wrong can cause large issues.<br />
</li><br />
<li><br />
Automate tasks. Automating tasks take a very good understanding of the software and goal.<br />
</li><br />
</ul><br />
<br />
'''Development''':<br />
<ul><br />
<li><br />
Naming<br />
<ul><br />
<li><br />
Avoid spaces.<br />
</li><br />
<li><br />
Use camelCase.<br />
</li><br />
<li><br />
Name common items with the common word starting each item.<br />
</li><br />
<li><br />
Name same item, but numbered with enough padding to sort correctly. ex: if going to at least 10 use 01-10 instead of 1-10.<br />
</li><br />
<li><br />
Name date by number not name and most general to specific. So they sort correctly. ex: 20161231 instead of Dec31-2016, etc.<br />
</li><br />
<li><br />
Name using noun first then verb. ex: logCreate, logList, dateStart, dateEnd, etc.<br />
</li><br />
</ul><br />
</li><br />
</ul><br />
<br />
<ul><br />
<li><br />
Coding<br />
<ul><br />
<li><br />
Top-down vs bottom-up design<br />
</li><br />
<li><br />
Always add comments...you may not remember what you did days, months, years from now<br />
</li><br />
<li><br />
Line block brackets up vertically<br />
</li><br />
<li><br />
Happy balance between elegance/complexity and readability/maintainability<br />
</li><br />
<li><br />
Happy balance between too long and too short variable naming<br />
</li><br />
<li><br />
Pick a style and stay consistent...this sometime means following someone else's style when modifying existing code<br />
</li><br />
<li><br />
Learn your debugging tool(s)...they can save a ton of time<br />
</li><br />
<li><br />
Give some thought to designing your log files...<br />
<ul><br />
<li><br />
Put the date and time in each record<br />
</li><br />
<li><br />
Format well...XML, JSON, delimited, etc.<br />
</li><br />
<li><br />
Make sure enough data is included to be helpful<br />
</li><br />
</ul><br />
</li><br />
</ul><br />
</li><br />
</ul><br />
<br />
'''*nix''':<br />
<br />
<ul><br />
<li><br />
Type "env" in the shell to display all the environment variables<br />
</li><br />
<li><br />
Use "set -x" to debug shell scripts ("set +x" turns it off)<br />
</li><br />
<li><br />
Use "set -o vi" to use vi to navigate/modify shell commands ("set +o" turns it off)<br />
</li><br />
<li><br />
crontab<br />
<ul><br />
<li><br />
Put number in 09 format to make easier to read, parse and sort (multiple spaces are fine)<br />
</li><br />
<li><br />
Always redirect command output somewhere, log file, /dev/null, etc., so it does not fill up your email<br />
</li><br />
</ul><br />
</li><br />
</ul><br />
<br />
<br />
'''SQL''':<br />
<br />
<ul><br />
<li><br />
Always use a where clause even if for everything...where 1 or where 1 = 1. This reminds someone editing the code that this query is operating on EVERYTHING. <br />
</li><br />
<li><br />
Comments are handy even in SQL for debugging and as comments. "--comments" is universal, but also /* comments */ in MySQL, {comments} in Informix, etc.<br />
</li><br />
<li><br />
Always comment out a drop statement right after executing so it is not accidentally run again<br />
</li><br />
<li><br />
Indexes are very important to the performance of a database<br />
</li><br />
<ul></div>Kemikohttps://wiki.kemiko.us/index.php?title=Informix&diff=391Informix2017-10-10T21:11:13Z<p>Kemiko: </p>
<hr />
<div>[https://en.wikipedia.org/wiki/IBM_Informix IBM Informix]<br />
<br />
This wiki article says, "Informix is generally considered to be optimized for environments with very low or no database administration, including use as an embedded database. It has a long track record of supporting very high transaction rates and providing uptime characteristics needed for mission critical applications such as manufacturing lines and reservation systems. Informix has been widely deployed in the retail sector, where the low administration overhead makes it useful for in-store deployments."<br />
<br />
<br />
I have worked with Informix in both manufacturing and reservations and find this to be true.<br />
<br />
<br />
I am currently working with <font color="red"><b>Informix 9.40.FC7 on HP-UX 11.11</b></font> as an adminisrator not a developer. We finally installed a new version of Informix...<font color="red"><b>12.10.FC7WE on RHEL 7.3</b></font>. However, I started with <font color="red"><b>MySQL and Informix C-ISAM on Linux</b></font>.<br />
<br />
*onstat commands are predefined queries that pull from the shared memory, sysmaster database, system files, etc.&nbsp;&nbsp;They are not output in the best format for reading or joining with other data...so use the sysmaster database to create your own reports with SQL joins&nbsp;&nbsp;([[Informix Monitoring]])<br />
*Learn the sysmaster database...this database holds configurations and statistics<br />
*ESQL/C is very fast for accessing the database (itop)<br />
*dbacces (output is vertical if width if greater than 80 characters) and isql are horrible SQL clients...use something like open source [http://squirrel-sql.sourceforge.net/ SQuirreL]<br />
*Every database has catalog tables that hold table, column, index information, etc. (select tabname from systables where tabid < 100;)<br />
*Find columns with SQL...select tabname, syscolumns.* from systables, syscolumns where systables.tabid = syscolumns.tabid and tabname = 'table';<br />
*Raw devices are faster<br />
*Optimize your statistics plan<br />
*HPL (High Performance Loader) is a very awkward GUI tool, but can unload and reload tables quicker using a raw data format<br />
*Create enough space for logical logging to prevent downtime if the tape fails. The engine will stop running if these logs can't be backed up<br />
*Large tables can really slow down OLTP databases<br />
*A "dummy" archive, ontape -s -L 0...w/TAPEDEV set to /dev/null (in onconfig), must be done after some configuration changes<br />
*Our Informix 9.40.FC7, which is 64 bit, has a 2GiB file limitation writing to HP-UX 11.11's file system...not the actual database data files going to a tape or pipe. So 9.40 can not archive a large database to disk without going through a pipe. 12.10 does not have this issue.<br />
*The system log only stamps the log with the date when the first record of the day is written...then only a time stamp is on the records.&nbsp;&nbsp;In 12.10 set "MSG_DATE 1" in the onconfig file.<br />
*Try and size your initial extents large enough that table spaces do not have a lot of additional extents (a physical unit of storage)<br />
*Informix date and time fields/functions are very different from MySQL<br />
*I really like some of Informix's SQL extensions...like "||" for concatenation, field[n,m] for substring, field matches( regexp ), etc.<br />
*Don't hit ctrl-c while starting the database (command oninit)...this will leave share memory in limbo<br />
*With Informix it is really easy to setup doing queries with two separate servers!<br />
*Do not "nice" dbaccess, etc. The engine handles the priority. Set MAX_PDQPRIORITY (Parallel Database Query) to process queries faster.<br />
*Informix is closely tied to the OS. Users and passwords are created and maintained by the OS.<br />
*Informix privileges are definitely different from MySQL. Informix has a "connect" grant that I like because it is the only privilges you need to revoke to deny a user access! Also, Informix can list "all" grants in one statement...MySQL can not!<br />
*<font color="red">Informix 12.10 has a single user mode...does MySQL? (read_only=1)</font><br />
*Informix has had descending btree indexes since 9.40, but MySQL will not have them until 8.0.<br />
*Informix "CURRENT" operator vs MySQL NOW() function.<br />
<br />
<br />
What are the differences between SQL statements with Informix and MySQL?&nbsp;&nbsp;(<font color="green">positive</font>/<font color="red">negative</font>/<font color="orange">neutral</font>)<br />
<table><br />
<tr><br />
<td><br />
Informix<br />
</td><br />
<td><br />
MySQL<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
database <database to use>;<br />
</td><br />
<td><br />
use <database to use>;<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
comments are: "<font color="orange"><b>{</b></font>" comment(s) "<font color="orange"><b>}</b></font>" or "<font color="orange"><b>--</b></font>"<br />
</td><br />
<td><br />
coments are: "<font color="orange"><b>/*</b></font>" comment(s) "<font color="orange"><b>*/</b></font>" or "<font color="orange"><b>--</b></font>"<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
<font color="red">A table NEEDS to be included in ALL select statements</font><br />
</td><br />
<td><br />
<font color="green">A table DOES NOT NEED to be included in select statements</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green"><b>MATCHES</b></font> <i><b>'regular_expr'</b></i> FROM <i><b>table</b></i><br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="red"><b>REGEXP</b></font> <i><b>'regular_expr'</b></i><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green"><b>||</b></font> <i><b>'select_expr'</b></i> FROM <i><b>table</b></i><br />
</td><br />
<td><br />
SELECT <font color="red">CONCAT(</font> <i><b>'select_expr'</b></i>, <i><b>'select_expr'</b></i> <font color="red">)</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <font color="red">FIRST i</font> <i><b>'select_expr'</b></i> FROM <i><b>table</b></i><br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green">LIMIT i</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> FROM <font color="red"><i><b>table</b></i> WHERE 1 = 1</font><br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green">WHERE 1</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr<font color="green">[i,j]</font>'</b></i> FROM <i><b>table</b></i> 1 = 1<br />
</td><br />
<td><br />
SELECT <font color="red">SUBSTR(</font> <i><b>'select_expr', <font color="red">i, j )</font> </b></i>WHERE 1<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <font color="red">CURRENT</font> FROM <i><b>systables</b></i> WHERE tabid = 1<br />
</td><br />
<td><br />
SELECT <font color="green">NOW( )</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <database>:systables.tabname, <database>:syscolumns.*<br />
FROM <database>:systables, <database>:syscolumns<br />
WHERE <database>:systables.tabid = <database>:syscolumns.tabid and <database>:systables.tabid > 100<br />
</td><br />
<td><br />
SELECT * FROM information_schema.columns WHERE table_schema = '<database>'; or DESCRIBE table<br />
</td><br />
</tr><br />
</table><br />
<br />
<br />
[https://www.ibm.com/developerworks/data/library/techarticle/dm-0801doe/ Compare the Informix Version 12 editions]</div>Kemikohttps://wiki.kemiko.us/index.php?title=Informix&diff=390Informix2017-10-02T15:10:48Z<p>Kemiko: </p>
<hr />
<div>[https://en.wikipedia.org/wiki/IBM_Informix IBM Informix]<br />
<br />
This wiki article says, "Informix is generally considered to be optimized for environments with very low or no database administration, including use as an embedded database. It has a long track record of supporting very high transaction rates and providing uptime characteristics needed for mission critical applications such as manufacturing lines and reservation systems. Informix has been widely deployed in the retail sector, where the low administration overhead makes it useful for in-store deployments."<br />
<br />
<br />
I have worked with Informix in both manufacturing and reservations and find this to be true.<br />
<br />
<br />
I am currently working with <font color="red"><b>Informix 9.40.FC7 on HP-UX 11.11</b></font> as an adminisrator not a developer. We finally installed a new version of Informix...<font color="red"><b>12.10.FC7WE on RHEL 7.3</b></font>. However, I started with <font color="red"><b>MySQL and Informix C-ISAM on Linux</b></font>.<br />
<br />
*onstat commands are predefined queries that pull from the shared memory, sysmaster database, system files, etc.&nbsp;&nbsp;They are not output in the best format for reading or joining with other data...so use the sysmaster database to create your own reports with SQL joins&nbsp;&nbsp;([[Informix Monitoring]])<br />
*Learn the sysmaster database...this database holds configurations and statistics<br />
*ESQL/C is very fast for accessing the database (itop)<br />
*dbacces (output is vertical if width if greater than 80 characters) and isql are horrible SQL clients...use something like open source [http://squirrel-sql.sourceforge.net/ SQuirreL]<br />
*Every database has catalog tables that hold table, column, index information, etc. (select tabname from systables where tabid < 100;)<br />
*Find columns with SQL...select tabname, syscolumns.* from systables, syscolumns where systables.tabid = syscolumns.tabid and tabname = 'table';<br />
*Raw devices are faster<br />
*Optimize your statistics plan<br />
*HPL (High Performance Loader) is a very awkward GUI tool, but can unload and reload tables quicker using a raw data format<br />
*Create enough space for logical logging to prevent downtime if the tape fails. The engine will stop running if these logs can't be backed up<br />
*Large tables can really slow down OLTP databases<br />
*A "dummy" archive, ontape -s -L 0...w/TAPEDEV set to /dev/null (in onconfig), must be done after some configuration changes<br />
*Our Informix 9.40.FC7, which is 64 bit, has a 2GiB file limitation writing to HP-UX 11.11's file system...not the actual database data files going to a tape or pipe. So 9.40 can not archive a large database to disk without going through a pipe. 12.10 does not have this issue.<br />
*The system log only stamps the log with the date when the first record of the day is written...then only a time stamp is on the records.&nbsp;&nbsp;In 12.10 set "MSG_DATE 1" in the onconfig file.<br />
*Try and size your initial extents large enough that table spaces do not have a lot of additional extents (a physical unit of storage)<br />
*Informix date and time fields/functions are very different from MySQL<br />
*I really like some of Informix's SQL extensions...like "||" for concatenation, field[n,m] for substring, field matches( regexp ), etc.<br />
*Don't hit ctrl-c while starting the database (command oninit)...this will leave share memory in limbo<br />
*With Informix it is really easy to setup doing queries with two separate servers!<br />
*Do not "nice" dbaccess, etc. The engine handles the priority. Set MAX_PDQPRIORITY (Parallel Database Query) to process queries faster.<br />
*Informix is closely tied to the OS. Users and passwords are created and maintained by the OS.<br />
*Informix privileges are definitely different from MySQL. Informix has a "connect" grant that I like because it is the only privilges you need to revoke to deny a user access! Also, Informix can list "all" grants in one statement...MySQL can not!<br />
*<font color="red">Informix 12.10 has a single user mode...does MySQL? (read_only=1)</font><br />
*INFORMIX "CURRENT" operator vs MySQL NOW() function.<br />
<br />
<br />
What are the differences between SQL statements with Informix and MySQL?&nbsp;&nbsp;(<font color="green">positive</font>/<font color="red">negative</font>/<font color="orange">neutral</font>)<br />
<table><br />
<tr><br />
<td><br />
Informix<br />
</td><br />
<td><br />
MySQL<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
database <database to use>;<br />
</td><br />
<td><br />
use <database to use>;<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
comments are: "<font color="orange"><b>{</b></font>" comment(s) "<font color="orange"><b>}</b></font>" or "<font color="orange"><b>--</b></font>"<br />
</td><br />
<td><br />
coments are: "<font color="orange"><b>/*</b></font>" comment(s) "<font color="orange"><b>*/</b></font>" or "<font color="orange"><b>--</b></font>"<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
<font color="red">A table NEEDS to be included in ALL select statements</font><br />
</td><br />
<td><br />
<font color="green">A table DOES NOT NEED to be included in select statements</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green"><b>MATCHES</b></font> <i><b>'regular_expr'</b></i> FROM <i><b>table</b></i><br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="red"><b>REGEXP</b></font> <i><b>'regular_expr'</b></i><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green"><b>||</b></font> <i><b>'select_expr'</b></i> FROM <i><b>table</b></i><br />
</td><br />
<td><br />
SELECT <font color="red">CONCAT(</font> <i><b>'select_expr'</b></i>, <i><b>'select_expr'</b></i> <font color="red">)</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <font color="red">FIRST i</font> <i><b>'select_expr'</b></i> FROM <i><b>table</b></i><br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green">LIMIT i</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> FROM <font color="red"><i><b>table</b></i> WHERE 1 = 1</font><br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green">WHERE 1</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr<font color="green">[i,j]</font>'</b></i> FROM <i><b>table</b></i> 1 = 1<br />
</td><br />
<td><br />
SELECT <font color="red">SUBSTR(</font> <i><b>'select_expr', <font color="red">i, j )</font> </b></i>WHERE 1<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <font color="red">CURRENT</font> FROM <i><b>systables</b></i> WHERE tabid = 1<br />
</td><br />
<td><br />
SELECT <font color="green">NOW( )</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <database>:systables.tabname, <database>:syscolumns.*<br />
FROM <database>:systables, <database>:syscolumns<br />
WHERE <database>:systables.tabid = <database>:syscolumns.tabid and <database>:systables.tabid > 100<br />
</td><br />
<td><br />
SELECT * FROM information_schema.columns WHERE table_schema = '<database>'; or DESCRIBE table<br />
</td><br />
</tr><br />
</table><br />
<br />
<br />
[https://www.ibm.com/developerworks/data/library/techarticle/dm-0801doe/ Compare the Informix Version 12 editions]</div>Kemikohttps://wiki.kemiko.us/index.php?title=Informix&diff=389Informix2017-09-29T18:03:33Z<p>Kemiko: </p>
<hr />
<div>[https://en.wikipedia.org/wiki/IBM_Informix IBM Informix]<br />
<br />
This wiki article says, "Informix is generally considered to be optimized for environments with very low or no database administration, including use as an embedded database. It has a long track record of supporting very high transaction rates and providing uptime characteristics needed for mission critical applications such as manufacturing lines and reservation systems. Informix has been widely deployed in the retail sector, where the low administration overhead makes it useful for in-store deployments."<br />
<br />
<br />
I have worked with Informix in both manufacturing and reservations and find this to be true.<br />
<br />
<br />
I am currently working with <font color="red"><b>Informix 9.40.FC7 on HP-UX 11.11</b></font> as an adminisrator not a developer. We finally installed a new version of Informix...<font color="red"><b>12.10.FC7WE on RHEL 7.3</b></font>. However, I started with <font color="red"><b>MySQL and Informix C-ISAM on Linux</b></font>.<br />
<br />
*onstat commands are predefined queries that pull from the shared memory, sysmaster database, system files, etc.&nbsp;&nbsp;They are not output in the best format for reading or joining with other data...so use the sysmaster database to create your own reports with SQL joins&nbsp;&nbsp;([[Informix Monitoring]])<br />
*Learn the sysmaster database...this database holds configurations and statistics<br />
*ESQL/C is very fast for accessing the database (itop)<br />
*dbacces (output is vertical if width if greater than 80 characters) and isql are horrible SQL clients...use something like open source [http://squirrel-sql.sourceforge.net/ SQuirreL]<br />
*Every database has catalog tables that hold table, column, index information, etc. (select tabname from systables where tabid < 100;)<br />
*Find columns with SQL...select tabname, syscolumns.* from systables, syscolumns where systables.tabid = syscolumns.tabid and tabname = 'table';<br />
*Raw devices are faster<br />
*Optimize your statistics plan<br />
*HPL (High Performance Loader) is a very awkward GUI tool, but can unload and reload tables quicker using a raw data format<br />
*Create enough space for logical logging to prevent downtime if the tape fails. The engine will stop running if these logs can't be backed up<br />
*Large tables can really slow down OLTP databases<br />
*A "dummy" archive, ontape -s -L 0...w/TAPEDEV set to /dev/null (in onconfig), must be done after some configuration changes<br />
*Our Informix 9.40.FC7, which is 64 bit, has a 2GiB file limitation writing to HP-UX 11.11's file system...not the actual database data files going to a tape or pipe. So 9.40 can not archive a large database to disk without going through a pipe. 12.10 does not have this issue.<br />
*The system log only stamps the log with the date when the first record of the day is written...then only a time stamp is on the records.&nbsp;&nbsp;In 12.10 set "MSG_DATE 1" in the onconfig file.<br />
*Try and size your initial extents large enough that table spaces do not have a lot of additional extents (a physical unit of storage)<br />
*Informix date and time fields/functions are very different from MySQL<br />
*I really like some of Informix's SQL extensions...like "||" for concatenation, field[n,m] for substring, field matches( regexp ), etc.<br />
*Don't hit ctrl-c while starting the database (command oninit)...this will leave share memory in limbo<br />
*With Informix it is really easy to setup doing queries with two separate servers!<br />
*Do not "nice" dbaccess, etc. The engine handles the priority. Set MAX_PDQPRIORITY (Parallel Database Query) to process queries faster.<br />
*Informix is closely tied to the OS. Users and passwords are created and maintained by the OS.<br />
*Informix privileges are definitely different from MySQL. Informix has a "connect" grant that I like because it is the only privilges you need to revoke to deny a user access! Also, Informix can list "all" grants in one statement...MySQL can not!<br />
*<font color="red">Informix 12.10 has a single user mode...does MySQL? (read_only=1)</font><br />
*INFORMIX "CURRENT" operator vs MySQL NOW() function.<br />
<br />
<br />
What are the differences between SQL statements with Informix and MySQL?&nbsp;&nbsp;(<font color="green">positive</font>/<font color="red">negative</font>/<font color="orange">neutral</font>)<br />
<table><br />
<tr><br />
<td><br />
Informix<br />
</td><br />
<td><br />
MySQL<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
comments are: "<font color="orange"><b>{</b></font>" comment(s) "<font color="orange"><b>}</b></font>" or "<font color="orange"><b>--</b></font>"<br />
</td><br />
<td><br />
coments are: "<font color="orange"><b>/*</b></font>" comment(s) "<font color="orange"><b>*/</b></font>" or "<font color="orange"><b>--</b></font>"<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
<font color="red">A table NEEDS to be included in ALL select statements</font><br />
</td><br />
<td><br />
<font color="green">A table DOES NOT NEED to be included in select statements</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green"><b>MATCHES</b></font> <i><b>'regular_expr'</b></i> FROM <i><b>table</b></i><br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="red"><b>REGEXP</b></font> <i><b>'regular_expr'</b></i><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green"><b>||</b></font> <i><b>'select_expr'</b></i> FROM <i><b>table</b></i><br />
</td><br />
<td><br />
SELECT <font color="red">CONCAT(</font> <i><b>'select_expr'</b></i>, <i><b>'select_expr'</b></i> <font color="red">)</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <font color="red">FIRST i</font> <i><b>'select_expr'</b></i> FROM <i><b>table</b></i><br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green">LIMIT i</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> FROM <font color="red"><i><b>table</b></i> WHERE 1 = 1</font><br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green">WHERE 1</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr<font color="green">[i,j]</font>'</b></i> FROM <i><b>table</b></i> 1 = 1<br />
</td><br />
<td><br />
SELECT <font color="red">SUBSTR(</font> <i><b>'select_expr', <font color="red">i, j )</font> </b></i>WHERE 1<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <font color="red">CURRENT</font> FROM <i><b>systables</b></i> WHERE tabid = 1<br />
</td><br />
<td><br />
SELECT <font color="green">NOW( )</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <database>:systables.tabname, <database>:syscolumns.*<br />
FROM <database>:systables, <database>:syscolumns<br />
WHERE <database>:systables.tabid = <database>:syscolumns.tabid and <database>:systables.tabid > 100<br />
</td><br />
<td><br />
SELECT * FROM information_schema.columns WHERE table_schema = '<database>'; or DESCRIBE table<br />
</td><br />
</tr><br />
</table><br />
<br />
<br />
[https://www.ibm.com/developerworks/data/library/techarticle/dm-0801doe/ Compare the Informix Version 12 editions]</div>Kemikohttps://wiki.kemiko.us/index.php?title=Informix&diff=388Informix2017-09-29T17:11:31Z<p>Kemiko: </p>
<hr />
<div>[https://en.wikipedia.org/wiki/IBM_Informix IBM Informix]<br />
<br />
This wiki article says, "Informix is generally considered to be optimized for environments with very low or no database administration, including use as an embedded database. It has a long track record of supporting very high transaction rates and providing uptime characteristics needed for mission critical applications such as manufacturing lines and reservation systems. Informix has been widely deployed in the retail sector, where the low administration overhead makes it useful for in-store deployments."<br />
<br />
<br />
I have worked with Informix in both manufacturing and reservations and find this to be true.<br />
<br />
<br />
I am currently working with <font color="red"><b>Informix 9.40.FC7 on HP-UX 11.11</b></font> as an adminisrator not a developer. We finally installed a new version of Informix...<font color="red"><b>12.10.FC7WE on RHEL 7.3</b></font>. However, I started with <font color="red"><b>MySQL and Informix C-ISAM on Linux</b></font>.<br />
<br />
*onstat commands are predefined queries that pull from the shared memory, sysmaster database, system files, etc.&nbsp;&nbsp;They are not output in the best format for reading or joining with other data...so use the sysmaster database to create your own reports with SQL joins&nbsp;&nbsp;([[Informix Monitoring]])<br />
*Learn the sysmaster database...this database holds configurations and statistics<br />
*ESQL/C is very fast for accessing the database (itop)<br />
*dbacces (output is vertical if width if greater than 80 characters) and isql are horrible SQL clients...use something like open source [http://squirrel-sql.sourceforge.net/ SQuirreL]<br />
*Every database has catalog tables that hold table, column, index information, etc. (select tabname from systables where tabid < 100;)<br />
*Find columns with SQL...select tabname, syscolumns.* from systables, syscolumns where systables.tabid = syscolumns.tabid and tabname = 'table';<br />
*Raw devices are faster<br />
*Optimize your statistics plan<br />
*HPL (High Performance Loader) is a very awkward GUI tool, but can unload and reload tables quicker using a raw data format<br />
*Create enough space for logical logging to prevent downtime if the tape fails. The engine will stop running if these logs can't be backed up<br />
*Large tables can really slow down OLTP databases<br />
*A "dummy" archive, ontape -s -L 0...w/TAPEDEV set to /dev/null (in onconfig), must be done after some configuration changes<br />
*Our Informix 9.40.FC7, which is 64 bit, has a 2GiB file limitation writing to HP-UX 11.11's file system...not the actual database data files going to a tape or pipe. So 9.40 can not archive a large database to disk without going through a pipe. 12.10 does not have this issue.<br />
*The system log only stamps the log with the date when the first record of the day is written...then only a time stamp is on the records.&nbsp;&nbsp;In 12.10 set "MSG_DATE 1" in the onconfig file.<br />
*Try and size your initial extents large enough that table spaces do not have a lot of additional extents (a physical unit of storage)<br />
*Informix date and time fields/functions are very different from MySQL<br />
*I really like some of Informix's SQL extensions...like "||" for concatenation, field[n,m] for substring, field matches( regexp ), etc.<br />
*Don't hit ctrl-c while starting the database (command oninit)...this will leave share memory in limbo<br />
*With Informix it is really easy to setup doing queries with two separate servers!<br />
*Do not "nice" dbaccess, etc. The engine handles the priority. Set MAX_PDQPRIORITY (Parallel Database Query) to process queries faster.<br />
*Informix is closely tied to the OS. Users and passwords are created and maintained by the OS.<br />
*Informix privileges are definitely different from MySQL. Informix has a "connect" grant that I like because it is the only privilges you need to revoke to deny a user access! Also, Informix can list "all" grants in one statement...MySQL can not!<br />
*<font color="red">Informix 12.10 has a single user mode...does MySQL? (read_only=1)</font><br />
<br />
<br />
What are the differences between SQL statements with Informix and MySQL?&nbsp;&nbsp;(<font color="green">positive</font>/<font color="red">negative</font>/<font color="orange">neutral</font>)<br />
<table><br />
<tr><br />
<td><br />
Informix<br />
</td><br />
<td><br />
MySQL<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
comments are: "<font color="orange"><b>{</b></font>" comment(s) "<font color="orange"><b>}</b></font>" or "<font color="orange"><b>--</b></font>"<br />
</td><br />
<td><br />
coments are: "<font color="orange"><b>/*</b></font>" comment(s) "<font color="orange"><b>*/</b></font>" or "<font color="orange"><b>--</b></font>"<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
<font color="red">A table NEEDS to be included in ALL select statements</font><br />
</td><br />
<td><br />
<font color="green">A table DOES NOT NEED to be included in select statements</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green"><b>MATCHES</b></font> <i><b>'regular_expr'</b></i> FROM <i><b>table</b></i><br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="red"><b>REGEXP</b></font> <i><b>'regular_expr'</b></i><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green"><b>||</b></font> <i><b>'select_expr'</b></i> FROM <i><b>table</b></i><br />
</td><br />
<td><br />
SELECT <font color="red">CONCAT(</font> <i><b>'select_expr'</b></i>, <i><b>'select_expr'</b></i> <font color="red">)</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <font color="red">FIRST i</font> <i><b>'select_expr'</b></i> FROM <i><b>table</b></i><br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green">LIMIT i</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> FROM <font color="red"><i><b>table</b></i> WHERE 1 = 1</font><br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green">WHERE 1</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr<font color="green">[i,j]</font>'</b></i> FROM <i><b>table</b></i> 1 = 1<br />
</td><br />
<td><br />
SELECT <font color="red">SUBSTR(</font> <i><b>'select_expr', <font color="red">i, j )</font> </b></i>WHERE 1<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <font color="red">CURRENT</font> FROM <i><b>systables</b></i> WHERE tabid = 1<br />
</td><br />
<td><br />
SELECT <font color="green">NOW( )</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <database>:systables.tabname, <database>:syscolumns.*<br />
FROM <database>:systables, <database>:syscolumns<br />
WHERE <database>:systables.tabid = <database>:syscolumns.tabid and <database>:systables.tabid > 100<br />
</td><br />
<td><br />
SELECT * FROM information_schema.columns WHERE table_schema = '<database>'; or DESCRIBE table<br />
</td><br />
</tr><br />
</table><br />
<br />
<br />
[https://www.ibm.com/developerworks/data/library/techarticle/dm-0801doe/ Compare the Informix Version 12 editions]</div>Kemikohttps://wiki.kemiko.us/index.php?title=Informix&diff=387Informix2017-09-29T17:10:50Z<p>Kemiko: </p>
<hr />
<div>[https://en.wikipedia.org/wiki/IBM_Informix IBM Informix]<br />
<br />
This wiki article says, "Informix is generally considered to be optimized for environments with very low or no database administration, including use as an embedded database. It has a long track record of supporting very high transaction rates and providing uptime characteristics needed for mission critical applications such as manufacturing lines and reservation systems. Informix has been widely deployed in the retail sector, where the low administration overhead makes it useful for in-store deployments."<br />
<br />
<br />
I have worked with Informix in both manufacturing and reservations and find this to be true.<br />
<br />
<br />
I am currently working with <font color="red"><b>Informix 9.40.FC7 on HP-UX 11.11</b></font> as an adminisrator not a developer. We finally installed a new version of Informix...<font color="red"><b>12.10.FC7WE on RHEL 7.3</b></font>. However, I started with <font color="red"><b>MySQL and Informix C-ISAM on Linux</b></font>.<br />
<br />
*onstat commands are predefined queries that pull from the shared memory, sysmaster database, system files, etc.&nbsp;&nbsp;They are not output in the best format for reading or joining with other data...so use the sysmaster database to create your own reports with SQL joins&nbsp;&nbsp;([[Informix Monitoring]])<br />
*Learn the sysmaster database...this database holds configurations and statistics<br />
*ESQL/C is very fast for accessing the database (itop)<br />
*dbacces (output is vertical if width if greater than 80 characters) and isql are horrible SQL clients...use something like open source [http://squirrel-sql.sourceforge.net/ SQuirreL]<br />
*Every database has catalog tables that hold table, column, index information, etc. (select tabname from systables where tabid < 100;)<br />
*Find columns with SQL...select tabname, syscolumns.* from systables, syscolumns where systables.tabid = syscolumns.tabid and tabname = 'table';<br />
*Raw devices are faster<br />
*Optimize your statistics plan<br />
*HPL (High Performance Loader) is a very awkward GUI tool, but can unload and reload tables quicker using a raw data format<br />
*Create enough space for logical logging to prevent downtime if the tape fails. The engine will stop running if these logs can't be backed up<br />
*Large tables can really slow down OLTP databases<br />
*A "dummy" archive, ontape -s -L 0...w/TAPEDEV set to /dev/null (in onconfig), must be done after some configuration changes<br />
*Our Informix 9.40.FC7, which is 64 bit, has a 2GiB file limitation writing to HP-UX 11.11's file system...not the actual database data files going to a tape or pipe. So 9.40 can not archive a large database to disk without going through a pipe. 12.10 does not have this issue.<br />
*The system log only stamps the log with the date when the first record of the day is written...then only a time stamp is on the records.&nbsp;&nbsp;In 12.10 set "MSG_DATE 1" in the onconfig file.<br />
*Try and size your initial extents large enough that table spaces do not have a lot of additional extents (a physical unit of storage)<br />
*Informix date and time fields/functions are very different from MySQL<br />
*I really like some of Informix's SQL extensions...like "||" for concatenation, field[n,m] for substring, field matches( regexp ), etc.<br />
*Don't hit ctrl-c while starting the database (command oninit)...this will leave share memory in limbo<br />
*With Informix it is really easy to setup doing queries with two separate servers!<br />
*Do not "nice" dbaccess, etc. The engine handles the priority. Set MAX_PDQPRIORITY (Parallel Database Query) to process queries faster.<br />
*Informix is closely tied to the OS. Users and passwords are created and maintained by the OS.<br />
*Informix privileges are definitely different from MySQL. Informix has a "connect" grant that I like because it is the only privilges you need to revoke to deny a user access! Also, Informix can list "all" grants in one statement...MySQL can not!<br />
*<font color="red">Informix 12.10 has a single user mode...does MySQL?</font><br />
<br />
<br />
What are the differences between SQL statements with Informix and MySQL?&nbsp;&nbsp;(<font color="green">positive</font>/<font color="red">negative</font>/<font color="orange">neutral</font>)<br />
<table><br />
<tr><br />
<td><br />
Informix<br />
</td><br />
<td><br />
MySQL<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
comments are: "<font color="orange"><b>{</b></font>" comment(s) "<font color="orange"><b>}</b></font>" or "<font color="orange"><b>--</b></font>"<br />
</td><br />
<td><br />
coments are: "<font color="orange"><b>/*</b></font>" comment(s) "<font color="orange"><b>*/</b></font>" or "<font color="orange"><b>--</b></font>"<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
<font color="red">A table NEEDS to be included in ALL select statements</font><br />
</td><br />
<td><br />
<font color="green">A table DOES NOT NEED to be included in select statements</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green"><b>MATCHES</b></font> <i><b>'regular_expr'</b></i> FROM <i><b>table</b></i><br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="red"><b>REGEXP</b></font> <i><b>'regular_expr'</b></i><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green"><b>||</b></font> <i><b>'select_expr'</b></i> FROM <i><b>table</b></i><br />
</td><br />
<td><br />
SELECT <font color="red">CONCAT(</font> <i><b>'select_expr'</b></i>, <i><b>'select_expr'</b></i> <font color="red">)</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <font color="red">FIRST i</font> <i><b>'select_expr'</b></i> FROM <i><b>table</b></i><br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green">LIMIT i</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> FROM <font color="red"><i><b>table</b></i> WHERE 1 = 1</font><br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green">WHERE 1</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr<font color="green">[i,j]</font>'</b></i> FROM <i><b>table</b></i> 1 = 1<br />
</td><br />
<td><br />
SELECT <font color="red">SUBSTR(</font> <i><b>'select_expr', <font color="red">i, j )</font> </b></i>WHERE 1<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <font color="red">CURRENT</font> FROM <i><b>systables</b></i> WHERE tabid = 1<br />
</td><br />
<td><br />
SELECT <font color="green">NOW( )</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <database>:systables.tabname, <database>:syscolumns.*<br />
FROM <database>:systables, <database>:syscolumns<br />
WHERE <database>:systables.tabid = <database>:syscolumns.tabid and <database>:systables.tabid > 100<br />
</td><br />
<td><br />
SELECT * FROM information_schema.columns WHERE table_schema = '<database>'; or DESCRIBE table<br />
</td><br />
</tr><br />
</table><br />
<br />
<br />
[https://www.ibm.com/developerworks/data/library/techarticle/dm-0801doe/ Compare the Informix Version 12 editions]</div>Kemikohttps://wiki.kemiko.us/index.php?title=Informix&diff=386Informix2017-09-29T16:11:14Z<p>Kemiko: </p>
<hr />
<div>[https://en.wikipedia.org/wiki/IBM_Informix IBM Informix]<br />
<br />
This wiki article says, "Informix is generally considered to be optimized for environments with very low or no database administration, including use as an embedded database. It has a long track record of supporting very high transaction rates and providing uptime characteristics needed for mission critical applications such as manufacturing lines and reservation systems. Informix has been widely deployed in the retail sector, where the low administration overhead makes it useful for in-store deployments."<br />
<br />
<br />
I have worked with Informix in both manufacturing and reservations and find this to be true.<br />
<br />
<br />
I am currently working with <font color="red"><b>Informix 9.40.FC7 on HP-UX 11.11</b></font> as an adminisrator not a developer. We finally installed a new version of Informix...<font color="red"><b>12.10.FC7WE on RHEL 7.3</b></font>. However, I started with <font color="red"><b>MySQL and Informix C-ISAM on Linux</b></font>.<br />
<br />
*onstat commands are predefined queries that pull from the shared memory, sysmaster database, system files, etc.&nbsp;&nbsp;They are not output in the best format for reading or joining with other data...so use the sysmaster database to create your own reports with SQL joins&nbsp;&nbsp;([[Informix Monitoring]])<br />
*Learn the sysmaster database...this database holds configurations and statistics<br />
*ESQL/C is very fast for accessing the database (itop)<br />
*dbacces (output is vertical if width if greater than 80 characters) and isql are horrible SQL clients...use something like open source [http://squirrel-sql.sourceforge.net/ SQuirreL]<br />
*Every database has catalog tables that hold table, column, index information, etc. (select tabname from systables where tabid < 100;)<br />
*Find columns with SQL...select tabname, syscolumns.* from systables, syscolumns where systables.tabid = syscolumns.tabid and tabname = 'table';<br />
*Raw devices are faster<br />
*Optimize your statistics plan<br />
*HPL (High Performance Loader) is a very awkward GUI tool, but can unload and reload tables quicker using a raw data format<br />
*Create enough space for logical logging to prevent downtime if the tape fails. The engine will stop running if these logs can't be backed up<br />
*Large tables can really slow down OLTP databases<br />
*A "dummy" archive, ontape -s -L 0...w/TAPEDEV set to /dev/null (in onconfig), must be done after some configuration changes<br />
*Our Informix 9.40.FC7, which is 64 bit, has a 2GiB file limitation writing to HP-UX 11.11's file system...not the actual database data files going to a tape or pipe. So 9.40 can not archive a large database to disk without going through a pipe. 12.10 does not have this issue.<br />
*The system log only stamps the log with the date when the first record of the day is written...then only a time stamp is on the records.&nbsp;&nbsp;In 12.10 set "MSG_DATE 1" in the onconfig file.<br />
*Try and size your initial extents large enough that table spaces do not have a lot of additional extents (a physical unit of storage)<br />
*Informix date and time fields/functions are very different from MySQL<br />
*I really like some of Informix's SQL extensions...like "||" for concatenation, field[n,m] for substring, field matches( regexp ), etc.<br />
*Don't hit ctrl-c while starting the database (command oninit)...this will leave share memory in limbo<br />
*With Informix it is really easy to setup doing queries with two separate servers!<br />
*Do not "nice" dbaccess, etc. The engine handles the priority. Set MAX_PDQPRIORITY (Parallel Database Query) to process queries faster.<br />
*Informix is closely tied to the OS. Users and passwords are created and maintained by the OS.<br />
*Informix privileges are definitely different from MySQL. Informix has a "connect" grant that I like because it is the only privilges you need to revoke to deny a user access! Also, Informix can list "all" grants in one statement...MySQL can not!<br />
<br />
<br />
What are the differences between SQL statements with Informix and MySQL?&nbsp;&nbsp;(<font color="green">positive</font>/<font color="red">negative</font>/<font color="orange">neutral</font>)<br />
<table><br />
<tr><br />
<td><br />
Informix<br />
</td><br />
<td><br />
MySQL<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
comments are: "<font color="orange"><b>{</b></font>" comment(s) "<font color="orange"><b>}</b></font>" or "<font color="orange"><b>--</b></font>"<br />
</td><br />
<td><br />
coments are: "<font color="orange"><b>/*</b></font>" comment(s) "<font color="orange"><b>*/</b></font>" or "<font color="orange"><b>--</b></font>"<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
<font color="red">A table NEEDS to be included in ALL select statements</font><br />
</td><br />
<td><br />
<font color="green">A table DOES NOT NEED to be included in select statements</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green"><b>MATCHES</b></font> <i><b>'regular_expr'</b></i> FROM <i><b>table</b></i><br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="red"><b>REGEXP</b></font> <i><b>'regular_expr'</b></i><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green"><b>||</b></font> <i><b>'select_expr'</b></i> FROM <i><b>table</b></i><br />
</td><br />
<td><br />
SELECT <font color="red">CONCAT(</font> <i><b>'select_expr'</b></i>, <i><b>'select_expr'</b></i> <font color="red">)</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <font color="red">FIRST i</font> <i><b>'select_expr'</b></i> FROM <i><b>table</b></i><br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green">LIMIT i</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> FROM <font color="red"><i><b>table</b></i> WHERE 1 = 1</font><br />
</td><br />
<td><br />
SELECT <i><b>'select_expr'</b></i> <font color="green">WHERE 1</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <i><b>'select_expr<font color="green">[i,j]</font>'</b></i> FROM <i><b>table</b></i> 1 = 1<br />
</td><br />
<td><br />
SELECT <font color="red">SUBSTR(</font> <i><b>'select_expr', <font color="red">i, j )</font> </b></i>WHERE 1<br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <font color="red">CURRENT</font> FROM <i><b>systables</b></i> WHERE tabid = 1<br />
</td><br />
<td><br />
SELECT <font color="green">NOW( )</font><br />
</td><br />
</tr><br />
<tr><br />
<td><br />
SELECT <database>:systables.tabname, <database>:syscolumns.*<br />
FROM <database>:systables, <database>:syscolumns<br />
WHERE <database>:systables.tabid = <database>:syscolumns.tabid and <database>:systables.tabid > 100<br />
</td><br />
<td><br />
SELECT * FROM information_schema.columns WHERE table_schema = '<database>'; or DESCRIBE table<br />
</td><br />
</tr><br />
</table><br />
<br />
<br />
[https://www.ibm.com/developerworks/data/library/techarticle/dm-0801doe/ Compare the Informix Version 12 editions]</div>Kemikohttps://wiki.kemiko.us/index.php?title=Database_101&diff=385Database 1012017-08-26T05:10:22Z<p>Kemiko: Created page with "* Always do a "select" before a "delete" * Rename objects before deleting * Always use a "where" clause..."where 1" or "where 1 = 1" for all * Self joins can be handy * Use AN..."</p>
<hr />
<div>* Always do a "select" before a "delete"<br />
* Rename objects before deleting<br />
* Always use a "where" clause..."where 1" or "where 1 = 1" for all<br />
* Self joins can be handy<br />
* Use ANSI joins for clarity</div>Kemikohttps://wiki.kemiko.us/index.php?title=Computer&diff=384Computer2017-08-26T05:07:03Z<p>Kemiko: </p>
<hr />
<div>[[Computers 101]]<br />
<br />
[[Database 101]]<br />
<br />
[[Important Dates]]<br />
<br />
[http://www.computerweekly.com/news/1280090622/The-first-ever-20-domain-names-registered The first ever 20 domain names registered]<br />
<br />
[[Linux]]<br />
<br />
[[Visual Editor (VI)]]<br />
<br />
[[Tech Tips]]<br />
<br />
[[Interesting Reading]]<br />
<br />
[[Informix]]<br />
<br />
[http://www.computerhistory.org/timeline/computers/ Timeline of Computer History]<br />
<br />
[http://www.computerweekly.com/news/2240103681/IT-greats-Top-10-greatest-IT-people IT greats: Top 10 greatest IT people]<br />
<br />
[http://www.computersciencedegreehub.com/30-most-influential-computer-scientists-alive-today/ The 30 Most Influential Computer Scientists Alive Today]<br />
<br />
[https://en.wikipedia.org/wiki/Multiversion_concurrency_control Multiversion concurrency control]<br />
<br />
[http://www.codejacked.com/know-your-keyboard-bang-splat-whack/ Know Your Keyboard: Bang, Splat, Whack!]<br />
<br />
[http://www.pcworld.com/article/116572/article.html Busting the Biggest PC Myths]<br />
<br />
[http://beta.phpformatter.com/ PHP formatter beta]</div>Kemikohttps://wiki.kemiko.us/index.php?title=Computers_101&diff=383Computers 1012017-08-26T05:06:44Z<p>Kemiko: </p>
<hr />
<div>* All computers are the same they use the same basic logic, storage etc.<br />
* Always make backups. Storage is cheap...so better to save too much than too little.<br />
* Many times the problem/solution is simple...don't over think it, but thought is good.<br />
* When accessing files/records without a sort (natural) they display as stored on disk. Usually by time at first, but becomes mixed as old files/records are deleted and new files/records are added.<br />
* Remember that everything is ones and zeros to a computer. So, letters and other data types are still just numbers.<br />
* Always do a select before a delete with everything...file system, database, application, etc.<br />
* When working with databases always rename objects before dropping...<br />
*Remember a little change can have large effects!</div>Kemikohttps://wiki.kemiko.us/index.php?title=Computer&diff=382Computer2017-08-26T05:03:05Z<p>Kemiko: </p>
<hr />
<div>[[Computers 101]]<br />
<br />
[[Important Dates]]<br />
<br />
[http://www.computerweekly.com/news/1280090622/The-first-ever-20-domain-names-registered The first ever 20 domain names registered]<br />
<br />
[[Linux]]<br />
<br />
[[Visual Editor (VI)]]<br />
<br />
[[Tech Tips]]<br />
<br />
[[Interesting Reading]]<br />
<br />
[[Informix]]<br />
<br />
[http://www.computerhistory.org/timeline/computers/ Timeline of Computer History]<br />
<br />
[http://www.computerweekly.com/news/2240103681/IT-greats-Top-10-greatest-IT-people IT greats: Top 10 greatest IT people]<br />
<br />
[http://www.computersciencedegreehub.com/30-most-influential-computer-scientists-alive-today/ The 30 Most Influential Computer Scientists Alive Today]<br />
<br />
[https://en.wikipedia.org/wiki/Multiversion_concurrency_control Multiversion concurrency control]<br />
<br />
[http://www.codejacked.com/know-your-keyboard-bang-splat-whack/ Know Your Keyboard: Bang, Splat, Whack!]<br />
<br />
[http://www.pcworld.com/article/116572/article.html Busting the Biggest PC Myths]<br />
<br />
[http://beta.phpformatter.com/ PHP formatter beta]</div>Kemikohttps://wiki.kemiko.us/index.php?title=Important_Dates&diff=381Important Dates2017-08-26T05:01:19Z<p>Kemiko: Created page with "[https://www.livescience.com/20718-computer-history.html History of Computers: A Brief Timeline] [http://www.datesandevents.org/events-timelines/07-computer-history-timeline...."</p>
<hr />
<div>[https://www.livescience.com/20718-computer-history.html History of Computers: A Brief Timeline]<br />
<br />
[http://www.datesandevents.org/events-timelines/07-computer-history-timeline.htm Computer History Timeline]<br />
<br />
My simple list:<br />
telephone<br />
transistor<br />
computer<br />
calculator<br />
C<br />
UNIX<br />
Linux</div>Kemikohttps://wiki.kemiko.us/index.php?title=Computer&diff=380Computer2017-08-26T04:06:46Z<p>Kemiko: </p>
<hr />
<div>[[Computers 101]]<br />
<br />
[[Important Dates]]<br />
<br />
[[Linux]]<br />
<br />
[[Visual Editor (VI)]]<br />
<br />
[[Tech Tips]]<br />
<br />
[[Interesting Reading]]<br />
<br />
[[Informix]]<br />
<br />
[http://www.computerhistory.org/timeline/computers/ Timeline of Computer History]<br />
<br />
[http://www.computerweekly.com/news/2240103681/IT-greats-Top-10-greatest-IT-people IT greats: Top 10 greatest IT people]<br />
<br />
[http://www.computersciencedegreehub.com/30-most-influential-computer-scientists-alive-today/ The 30 Most Influential Computer Scientists Alive Today]<br />
<br />
[https://en.wikipedia.org/wiki/Multiversion_concurrency_control Multiversion concurrency control]<br />
<br />
[http://www.codejacked.com/know-your-keyboard-bang-splat-whack/ Know Your Keyboard: Bang, Splat, Whack!]<br />
<br />
[http://www.pcworld.com/article/116572/article.html Busting the Biggest PC Myths]<br />
<br />
[http://beta.phpformatter.com/ PHP formatter beta]</div>Kemiko