defaria.com/blogs/Status/archives/2007_04.html

   1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
   2    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
   3 <html xmlns="http://www.w3.org/1999/xhtml" id="sixapart-standard">
   4 <head>
   5    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
   6    <meta name="generator" content="Movable Type 5.2.3" />
   7
   8    <link rel="stylesheet" href="http://defaria.com/blogs/Status/styles-site.css" type="text/css" />
   9    <link rel="alternate" type="application/atom+xml" title="Atom" href="http://defaria.com/blogs/Status/atom.xml" />
  10    <link rel="alternate" type="application/rss+xml" title="RSS 2.0" href="http://defaria.com/blogs/Status/index.xml"$>" />
  11
  12    <title>Status for Andrew DeFaria: April 2007 Archives</title>
  13
  14    <link rel="start" href="http://defaria.com/blogs/Status/" title="Home" />
  15    <link rel="prev" href="http://defaria.com/blogs/Status/archives/2007_03.html" title="March 2007" />
  16    <link rel="next" href="http://defaria.com/blogs/Status/archives/2007_05.html" title="May 2007" />
  17 </head>
  18 <body class="layout-one-column">
  19    <div id="container">
  20       <div id="container-inner" class="pkg">
  21
  22          <div id="banner">
  23             <div id="banner-inner" class="pkg">
  24                <h1 id="banner-header"><a href="http://defaria.com/blogs/Status/" accesskey="1">Status for Andrew DeFaria</a></h1>
  25                <h2 id="banner-description">Searchable status reports and work log</h2>
  26             </div>
  27          </div>
  28
  29          <div id="pagebody">
  30             <div id="pagebody-inner" class="pkg">
  31                <div id="alpha">
  32                   <div id="alpha-inner" class="pkg">
  33
  34                      <p class="content-nav">
  35                         <a href="http://defaria.com/blogs/Status/archives/2007_03.html">&laquo; March 2007</a> |
  36                         <a href="http://defaria.com/blogs/Status/">Main</a>
  37                         | <a href="http://defaria.com/blogs/Status/archives/2007_05.html">May 2007 &raquo;</a>
  38                      </p>
  39
  40
  41                      <!--
  42 <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  43          xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/"
  44          xmlns:dc="http://purl.org/dc/elements/1.1/">
  45 <rdf:Description
  46     rdf:about="http://defaria.com/blogs/Status/archives/2007_04.html#entry-000636"
  47     trackback:ping="http://defaria.com/mt/mt-tb.cgi/24"
  48     dc:title="GPDB Enhancements/Fixes"
  49     dc:identifier="http://defaria.com/blogs/Status/archives/2007_04.html#entry-000636"
  50     dc:subject="GPDB"
  51     dc:description=" Implemented gpdb_deleteSiteDomain Modify site almost functionally complete Looking into how to do what MySQL does with it&apos;s limit clause in Oracle Changed List Projects at Site to be paged Changed how Projects are displayed Added most of the Project..."
  52     dc:creator=""
  53     dc:date="2007-04-30T14:58:37-06:00" />
  54 </rdf:RDF>
  55 -->
  56
  57
  58                      <h2 class="date-header">April 30, 2007</h2>
  59                      <a id="a000636"></a>
  60                      <div class="entry" id="entry-636">
  61                         <h3 class="entry-header">GPDB Enhancements/Fixes</h3>
  62                         <div class="entry-content">
  63                            <div class="entry-body">
  64                               <ul>
  65   <li>Implemented gpdb_deleteSiteDomain</li>
  66   <li>Modify site almost functionally complete</li>
  67   <li>Looking into how to do what MySQL does with it's limit clause in
  68 Oracle</li>
  69   <li>Changed List Projects at Site to be paged</li>
  70   <li>Changed how Projects are displayed </li>
  71   <li>Added most of the Project update page</li>
  72   <li>Change some of the logic on login/logout</li>
  73   <li>Change gpdb_putClearcase to set a global as to whether the record
  74 was added/updated or nothing changed.</li>
  75   <li>Changed gpdb_add_vob.pl to:</li>
  76   <ul>
  77     <li>Report better the number of Clearcase vob records added or not.</li>
  78   </ul>
  79   <ul>
  80     <li>Add an UNKNOWN project for the site it's running at (if needed)</li>
  81     <li>Properly select the appropriate UNKNOWN project</li>
  82   </ul>
  83 </ul>
  84
  85                               <p class="entry-footer">
  86                                  <span class="post-footers">Posted by  at  2:58 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000636.html">Permalink</a>
  87
  88                                  | <a href="http://defaria.com/blogs/Status/archives/000636.html#trackback">TrackBacks (0)</a>
  89                               </p>
  90                            </div>
  91                         </div>
  92                      </div>
  93
  94                      <!--
  95 <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  96          xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/"
  97          xmlns:dc="http://purl.org/dc/elements/1.1/">
  98 <rdf:Description
  99     rdf:about="http://defaria.com/blogs/Status/archives/2007_04.html#entry-000634"
 100     trackback:ping="http://defaria.com/mt/mt-tb.cgi/23"
 101     dc:title="Why MS Word is a bad HTML editor"
 102     dc:identifier="http://defaria.com/blogs/Status/archives/2007_04.html#entry-000634"
 103     dc:subject="Texas Instruments"
 104     dc:description=" Described a little bit about why MS Word is not a good HTML editor..."
 105     dc:creator=""
 106     dc:date="2007-04-21T20:56:37-06:00" />
 107 </rdf:RDF>
 108 -->
 109
 110
 111                      <h2 class="date-header">April 21, 2007</h2>
 112                      <a id="a000634"></a>
 113                      <div class="entry" id="entry-634">
 114                         <h3 class="entry-header">Why MS Word is a bad HTML editor</h3>
 115                         <div class="entry-content">
 116                            <div class="entry-body">
 117                               <ul>
 118   <li>Described a little bit about why MS Word is not a good HTML editor</li>
 119 </ul>
 120
 121                               <p>LeGrand, Christina wrote:</p>
 122
 123 <blockquote type=cite>
 124   <p>Larry, thanks for the great feedback! I have made the last three changes listed here - to the wording in the  "Just the FAQs" section, the "ITS
 125 in the Customer Success Story, and the URL in the LDM docs section. Great catches! For the first two suggestions, all secondary titles are Arial 11, so I am not sure why they look different in your Outlook, but I believe you that they do. If anyone knows of how to prevent this, please let me know!</p>
 126 </blockquote>
 127
 128 The proper way to "prevent" such things is to use the proper way to do
 129 such things. To do this one should follow the standards and then
 130 validate (as Regan said to Gorbachev "<a
 131  href="http://www.brainyquote.com/quotes/quotes/r/ronaldreag147717.html">Trust
 132 but verify</a>").<br>
 133 <br>
 134 HTML headers should be done with the "H" tags of which there are H1 -
 135 H6. IOW one should not be putting any kinds of font information such as
 136 Arial nor point size in there. Such presentation information is best
 137 left to the eventual reader, who may not have the font you've chosen
 138 nor want Wingbats in Pink at 24 point! <br>
 139 <br>
 140 However if you must code in a layout that's what CSS is for.<br>
 141 <br>
 142 In any event Word, which this was made with, is an absolutely horrible
 143 HTML editor! And I shall now show you some of the reasons why. I hope
 144 you'll enjoy this ride as much as I will...<br>
 145 <br>
 146 First off MS Word created HTML pages contain a lot of bloat. What Word
 147 does is include styling information at the beginning of the document to
 148 cover MS Word "styles" then applies "styles" to the layout. This is
 149 done, AFAICT, to attempt to get the web page to look "just like it did
 150 in Word". In a sentence - It's bad web design and bloat to your web
 151 pages let alone often non-standard and should be avoided at all costs.<br>
 152 <br>
 153 Here is the beginning bloat:<br>
 154 <blockquote>
 155   <pre id="line165">&lt;html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
 156 xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
 157 xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
 158 xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
 159 xmlns=3D<a class="moz-txt-link-rfc2396E" href="http://www.w3.org/TR/REC-html40">"http://www.w3.org/TR/REC-html40"</a>&gt;
 160
 161
 162 &lt;head&gt;
 163 &lt;meta http-equiv=3DContent-Type content=3D"text/html; =
 164 charset=3Dus-ascii"&gt;
 165 &lt;meta name=3DProgId content=3DWord.Document&gt;
 166 &lt;meta name=3DGenerator content=3D"Microsoft Word 11"&gt;
 167 &lt;meta name=3DOriginator content=3D"Microsoft Word 11"&gt;
 168 &lt;link rel=3DFile-List href=3D<a class="moz-txt-link-rfc2396E" href="cid:filelist.xml@01C78350.D624B260">"cid:filelist.xml@01C78350.D624B260"</a>&gt;
 169 &lt;link rel=3DEdit-Time-Data href=3D<a class="moz-txt-link-rfc2396E" href="cid:editdata.mso">"cid:editdata.mso"</a>&gt;
 170
 171 &lt;!--[if !mso]&gt;
 172 &lt;style&gt;
 173 v\:* {behavior:url(#default#VML);}
 174 o\:* {behavior:url(#default#VML);}
 175 w\:* {behavior:url(#default#VML);}
 176 .shape {behavior:url(#default#VML);}
 177   </pre>
 178   <pre id="line238">&lt;/style&gt;
 179 &lt;![endif]--&gt;&lt;o:SmartTagType
 180  namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
 181 name=3D"City"/&gt;
 182 &lt;o:SmartTagType =
 183 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 184  name=3D"PlaceType"/&gt;
 185 &lt;o:SmartTagType =
 186 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 187  name=3D"PlaceName"/&gt;
 188 &lt;o:SmartTagType =
 189 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 190  name=3D"place"/&gt;
 191
 192 &lt;o:SmartTagType =
 193 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 194  name=3D"PersonName"/&gt;
 195 &lt;!--[if gte mso 9]&gt;&lt;xml&gt;
 196  &lt;o:OfficeDocumentSettings&gt;
 197   &lt;o:DoNotRelyOnCSS/&gt;
 198  &lt;/o:OfficeDocumentSettings&gt;
 199 &lt;/xml&gt;&lt;![endif]--&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;
 200  &lt;w:WordDocument&gt;
 201   &lt;w:SpellingState&gt;Clean&lt;/w:SpellingState&gt;
 202   &lt;w:DocumentKind&gt;DocumentEmail&lt;/w:DocumentKind&gt;
 203   &lt;w:EnvelopeVis/&gt;
 204   &lt;w:ValidateAgainstSchemas/&gt;
 205   &lt;w:SaveIfXMLInvalid&gt;false&lt;/w:SaveIfXMLInvalid&gt;
 206   &lt;w:IgnoreMixedContent&gt;false&lt;/w:IgnoreMixedContent&gt;
 207   &lt;w:AlwaysShowPlaceholderText&gt;false&lt;/w:AlwaysShowPlaceholderText&gt;
 208   &lt;w:BrowserLevel&gt;MicrosoftInternetExplorer4&lt;/w:BrowserLevel&gt;
 209  &lt;/w:WordDocument&gt;
 210   </pre>
 211   <pre id="line269">&lt;/xml&gt;&lt;![endif]--&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;
 212  &lt;w:LatentStyles DefLockedState=3D"false" LatentStyleCount=3D"156"&gt;
 213  &lt;/w:LatentStyles&gt;
 214
 215 &lt;/xml&gt;&lt;![endif]--&gt;&lt;!--[if !mso]&gt;
 216 &lt;style&gt;
 217 st1\:*{behavior:url(#default#ieooui) }
 218 &lt;/style&gt;
 219 &lt;![endif]--&gt;
 220 &lt;style&gt;
 221 &lt;!--
 222  /* Font Definitions */
 223  @font-face
 224         {font-family:Tahoma;
 225         panose-1:2 11 6 4 3 5 4 4 2 4;
 226         mso-font-alt:Verdana;
 227         mso-font-charset:0;
 228         mso-generic-font-family:swiss;
 229         mso-font-pitch:variable;
 230         mso-font-signature:1627421319 -2147483648 8 0 66047 0;}
 231  /* Style Definitions */
 232  p.MsoNormal, li.MsoNormal, div.MsoNormal
 233         {mso-style-parent:"";
 234         margin:0in;
 235         margin-bottom:.0001pt;
 236         mso-pagination:widow-orphan;
 237         font-size:12.0pt;
 238         font-family:"Times New Roman";
 239         mso-fareast-font-family:"Times New Roman";
 240         color:black;}
 241 a:link, span.MsoHyperlink
 242         {color:blue;
 243         text-decoration:underline;
 244         text-underline:single;}
 245 a:visited, span.MsoHyperlinkFollowed
 246         {color:purple;
 247         text-decoration:underline;
 248         text-underline:single;}
 249 p
 250         {mso-margin-top-alt:auto;
 251         margin-right:0in;
 252         mso-margin-bottom-alt:auto;
 253         margin-left:0in;
 254         mso-pagination:widow-orphan;
 255         font-size:12.0pt;
 256         font-family:"Times New Roman";
 257         mso-fareast-font-family:"Times New Roman";
 258         color:black;}
 259 p.newslettertitle, li.newslettertitle, div.newslettertitle
 260         {mso-style-name:newslettertitle;
 261         mso-margin-top-alt:auto;
 262         margin-right:0in;
 263         mso-margin-bottom-alt:auto;
 264         margin-left:0in;
 265         mso-pagination:widow-orphan;
 266         font-size:12.0pt;
 267         font-family:"Times New Roman";
 268         mso-fareast-font-family:"Times New Roman";
 269         color:black;}
 270 p.newslettertext, li.newslettertext, div.newslettertext
 271         {mso-style-name:newslettertext;
 272         mso-margin-top-alt:auto;
 273         margin-right:0in;
 274         mso-margin-bottom-alt:auto;
 275         margin-left:0in;
 276         mso-pagination:widow-orphan;
 277         font-size:12.0pt;
 278         font-family:"Times New Roman";
 279         mso-fareast-font-family:"Times New Roman";
 280         color:black;}
 281 p.newsletterheading, li.newsletterheading, div.newsletterheading
 282         {mso-style-name:newsletterheading;
 283         mso-margin-top-alt:auto;
 284         margin-right:0in;
 285         mso-margin-bottom-alt:auto;
 286         margin-left:0in;
 287         mso-pagination:widow-orphan;
 288         font-size:12.0pt;
 289         font-family:"Times New Roman";
 290         mso-fareast-font-family:"Times New Roman";
 291         color:black;}
 292 p.newsletterbullet, li.newsletterbullet, div.newsletterbullet
 293         {mso-style-name:newsletterbullet;
 294         mso-margin-top-alt:auto;
 295         margin-right:0in;
 296         mso-margin-bottom-alt:auto;
 297         margin-left:0in;
 298         mso-pagination:widow-orphan;
 299         font-size:12.0pt;
 300         font-family:"Times New Roman";
 301         mso-fareast-font-family:"Times New Roman";
 302         color:black;}
 303 span.EmailStyle22
 304         {mso-style-type:personal;
 305         mso-style-noshow:yes;
 306         mso-ansi-font-size:10.0pt;
 307         mso-bidi-font-size:10.0pt;
 308         font-family:Arial;
 309         mso-ascii-font-family:Arial;
 310         mso-hansi-font-family:Arial;
 311         mso-bidi-font-family:Arial;}
 312 span.EmailStyle23
 313         {mso-style-type:personal;
 314         mso-style-noshow:yes;
 315         mso-ansi-font-size:10.0pt;
 316         mso-bidi-font-size:10.0pt;
 317         font-family:Arial;
 318         mso-ascii-font-family:Arial;
 319         mso-hansi-font-family:Arial;
 320         mso-bidi-font-family:Arial;
 321         color:navy;}
 322 span.EmailStyle24
 323         {mso-style-type:personal;
 324         mso-style-noshow:yes;
 325         mso-ansi-font-size:10.0pt;
 326         mso-bidi-font-size:10.0pt;
 327         font-family:Arial;
 328         mso-ascii-font-family:Arial;
 329         mso-hansi-font-family:Arial;
 330         mso-bidi-font-family:Arial;
 331         color:navy;}
 332 span.EmailStyle27
 333         {mso-style-type:personal-reply;
 334         mso-style-noshow:yes;
 335         mso-ansi-font-size:10.0pt;
 336         mso-bidi-font-size:10.0pt;
 337         font-family:Arial;
 338         mso-ascii-font-family:Arial;
 339         mso-hansi-font-family:Arial;
 340         mso-bidi-font-family:Arial;
 341         color:navy;}
 342 span.SpellE
 343         {mso-style-name:"";
 344         mso-spl-e:yes;}
 345 @page Section1
 346         {size:8.5in 11.0in;
 347         margin:1.0in 1.25in 1.0in 1.25in;
 348         mso-header-margin:.5in;
 349         mso-footer-margin:.5in;
 350         mso-paper-source:0;}
 351 div.Section1
 352         {page:Section1;}
 353 --&gt;
 354 &lt;/style&gt;
 355
 356 &lt;!--[if gte mso 10]&gt;
 357 &lt;style&gt;
 358  /* Style Definitions */=20
 359  table.MsoNormalTable
 360         {mso-style-name:"Table Normal";
 361         mso-tstyle-rowband-size:0;
 362         mso-tstyle-colband-size:0;
 363         mso-style-noshow:yes;
 364         mso-style-parent:"";
 365         mso-padding-alt:0in 5.4pt 0in 5.4pt;
 366         mso-para-margin:0in;
 367         mso-para-margin-bottom:.0001pt;
 368         mso-pagination:widow-orphan;
 369         font-size:10.0pt;
 370         font-family:"Times New Roman";
 371         mso-ansi-language:#0400;
 372         mso-fareast-language:#0400;
 373         mso-bidi-language:#0400;}
 374   </pre>
 375   <pre id="line430">&lt;/style&gt;
 376 &lt;![endif]--&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;
 377  &lt;o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" /&gt;
 378 &lt;/xml&gt;&lt;![endif]--&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;
 379  &lt;o:shapelayout v:ext=3D"edit"&gt;
 380   &lt;o:idmap v:ext=3D"edit" data=3D"1" /&gt;
 381  &lt;/o:shapelayout&gt;&lt;/xml&gt;&lt;![endif]--&gt;
 382
 383 &lt;/head&gt;
 384   </pre>
 385 </blockquote>
 386 Now wasn't that fun? <span class="moz-smiley-s1"><span> :-) </span></span><br>
 387 <br>
 388 After creating all that crud we are now able to apply it to our
 389 content. Here's the part that does the heading:<br>
 390 <blockquote><tt> &lt;p class=3Dnewsletterheading =<br>
 391 style=3D'mso-margin-top-alt:0in;margin-right:<br>
 392 0in;margin-bottom:4.0pt;margin-left:0in'&gt;&lt;span =<br>
 393 style=3D'mso-bookmark:OLE_LINK1'&gt;&lt;span<br>
 394 style=3D'mso-bookmark:OLE_LINK10'&gt;&lt;span =<br>
 395 style=3D'mso-bookmark:OLE_LINK11'&gt;&lt;span<br>
 396 style=3D'mso-bookmark:OLE_LINK12'&gt;&lt;span =<br>
 397 style=3D'mso-bookmark:OLE_LINK2'&gt;&lt;span<br>
 398 style=3D'mso-bookmark:OLE_LINK3'&gt;&lt;strong&gt;&lt;b&gt;&lt;font
 399 size=3D3 =<br>
 400 color=3Dblack<br>
 401 face=3DArial&gt;&lt;span =<br>
 402 style=3D'font-size:12.0pt;font-family:Arial;mso-bidi-font-style:<br>
 403 italic'&gt;DesignSync Documentation Has
 404 Moved&lt;/span&gt;&lt;/font&gt;&lt;span<br>
 405 =<br>
 406 style=3D'mso-bidi-font-style:italic'&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/b&gt;&lt;/strong&gt;&lt;/spa=<br>
 407 n&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;<br>
 408   </tt></blockquote>
 409 OK, not you tell me - where's the Arial 11 point in there?<br>
 410
 411 <br>
 412 I'm sure you've enjoyed the above exercise...<br>
 413 <br>
 414 Oh, and how does this look in "straight" HTML?<br>
 415 <blockquote><tt>&lt;h2&gt;DesignSync Documentation Has Moved&lt;/h2&gt;</tt><br>
 416 </blockquote>
 417
 418
 419                               <p class="entry-footer">
 420                                  <span class="post-footers">Posted by  at  8:56 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000634.html">Permalink</a>
 421
 422                                  | <a href="http://defaria.com/blogs/Status/archives/000634.html#trackback">TrackBacks (0)</a>
 423                               </p>
 424                            </div>
 425                         </div>
 426                      </div>
 427
 428                      <!--
 429 <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
 430          xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/"
 431          xmlns:dc="http://purl.org/dc/elements/1.1/">
 432 <rdf:Description
 433     rdf:about="http://defaria.com/blogs/Status/archives/2007_04.html#entry-000633"
 434     trackback:ping="http://defaria.com/mt/mt-tb.cgi/22"
 435     dc:title="Turning on HTML for Exchange/IMAP"
 436     dc:identifier="http://defaria.com/blogs/Status/archives/2007_04.html#entry-000633"
 437     dc:subject="Texas Instruments"
 438     dc:description=" Described how to configure Exchange&apos;s IMAP server to server out HTML..."
 439     dc:creator=""
 440     dc:date="2007-04-21T20:38:56-06:00" />
 441 </rdf:RDF>
 442 -->
 443
 444
 445
 446                      <a id="a000633"></a>
 447                      <div class="entry" id="entry-633">
 448                         <h3 class="entry-header">Turning on HTML for Exchange/IMAP</h3>
 449                         <div class="entry-content">
 450                            <div class="entry-body">
 451                               <ul>
 452   <li>Described how to configure Exchange's IMAP server to server out HTML</li>
 453 </ul>
 454
 455                               <p>I had worked on this before but I just want to document it here. I use Thunderbird and connect to Exchange servers via IMAP. Here at TI I was only getting plain text from the IMAP server. I was speaking to a friend of mine who managed an Exchange at a prior company we worked together at. I used TB and IMAP back then too and did not have problems with HTML'ized email from Outlook users:</p>
 456
 457 <b><font color="#204a87">Andrew DeFaria:</font></b> In any event I'm nore interested if you have an answer to my question regarding Exchange/IMAP.<br>
 458 <b><font color="#204a87">Andrew DeFaria:</font></b> How do you configure Exchange to sent HTML email to IMAP?<br>
 459 <b><font color="#cc0000">Ron Van Scherpe:</font></b> as far as imap goes,<br>
 460 <b><font color="#cc0000">Ron Van Scherpe:</font></b> we don't use it here.<br>
 461 <b><font color="#cc0000">Ron Van Scherpe:</font></b> but lemme check  something<br>
 462 <b><font color="#204a87">Andrew DeFaria:</font></b> I could have sworn that while at Salira I used TB and IMAP to your exchange server and when Outlook users sent HTML'ized email I saw it in TB as HTML'ized.<br>
 463 <b><font color="#204a87">Andrew DeFaria:</font></b> Here at TI all I get from the IMAP port is just plain text. Seems to me that this might be an Exchange setting....<br>
 464 <b><font color="#cc0000">Ron Van Scherpe:</font></b> yes..it's a server setting.<br>
 465 <b><font color="#cc0000">Ron Van Scherpe:</font></b> they must have it set for plain text only because you have 3 options..<br>
 466 <b><font color="#cc0000">Ron Van Scherpe:</font></b> plain text, HTML or both.<br>
 467 <b><font color="#cc0000">Ron Van Scherpe:</font></b> we have it set to both here<br>
 468 <b><font color="#cc0000">Ron Van Scherpe:</font></b> and we did at Salira.<br>
 469 <b><font color="#cc0000">Ron Van Scherpe:</font></b> they're taking an MS approach<br>
 470 <b><font color="#cc0000">Ron Van Scherpe:</font></b> they don't want HTML rendered hacks<br>
 471 <b><font color="#204a87">Andrew DeFaria:</font></b> HTML rendered hacks will happen more often in Outlook than TB is my guess.<br>
 472 <b><font color="#cc0000">Ron Van Scherpe:</font></b> login in to the Exchange server<br>
 473 <b><font color="#cc0000">Ron Van Scherpe:</font></b> open up ESM<br>
 474 <b><font color="#cc0000">Ron Van Scherpe:</font></b> expand the server so that you see the Protocols...<br>
 475 <b><font color="#cc0000">Ron Van Scherpe:</font></b> right click on the iMap virtual server and select properities<br>
 476 <b><font color="#cc0000">Ron Van Scherpe:</font></b> click on the message format tab and select rendering type<br>
 477 <b><font color="#cc0000">Ron Van Scherpe:</font></b> you'll have to restart the imap server<br>
 478 <b><font color="#204a87">Andrew DeFaria:</font></b> Great! And thanks! I'll send this along...<br>
 479 <b><font color="#204a87">Andrew DeFaria:</font></b> I owe you a beer (that is if they agree to it and implement it...)<br>
 480 <b><font color="#cc0000">Ron Van Scherpe:</font></b> $50<br>
 481 <b><font color="#204a87">Andrew DeFaria:</font></b> OK a case!<br>
 482 <b><font color="#cc0000">Ron Van Scherpe:</font></b> heh</p>
 483
 484
 485                               <p class="entry-footer">
 486                                  <span class="post-footers">Posted by  at  8:38 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000633.html">Permalink</a>
 487
 488                                  | <a href="http://defaria.com/blogs/Status/archives/000633.html#trackback">TrackBacks (0)</a>
 489                               </p>
 490                            </div>
 491                         </div>
 492                      </div>
 493
 494                      <!--
 495 <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
 496          xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/"
 497          xmlns:dc="http://purl.org/dc/elements/1.1/">
 498 <rdf:Description
 499     rdf:about="http://defaria.com/blogs/Status/archives/2007_04.html#entry-000632"
 500     trackback:ping="http://defaria.com/mt/mt-tb.cgi/21"
 501     dc:title="Oracle limit clause"
 502     dc:identifier="http://defaria.com/blogs/Status/archives/2007_04.html#entry-000632"
 503     dc:subject="GPDB"
 504     dc:description=" Modify site almost functionally complete Looking into how to do what MySQL does with it&apos;s limit clause in Oracle..."
 505     dc:creator=""
 506     dc:date="2007-04-18T19:04:09-06:00" />
 507 </rdf:RDF>
 508 -->
 509
 510
 511                      <h2 class="date-header">April 18, 2007</h2>
 512                      <a id="a000632"></a>
 513                      <div class="entry" id="entry-632">
 514                         <h3 class="entry-header">Oracle limit clause</h3>
 515                         <div class="entry-content">
 516                            <div class="entry-body">
 517                               <ul>
 518   <li>Modify site almost functionally complete</li>
 519
 520   <li>Looking into how to do what MySQL does with it's limit clause in Oracle</li>
 521 </ul>
 522
 523                               <h2>Oracle limit clause</h2>
 524
 525 <p>Found this ugly workaround for MySQL's limit clause:</p>
 526
 527 <div class=code><pre>
 528 select * from (
 529   select rownum as limit, t.* from (
 530     select * from &lt;table&gt; where &lt;condition&gt;
 531   )
 532 t) where limit between &lt;lower limit&gt; and &lt;upper limit&gt;
 533 </pre></div>
 534
 535 <p>Hey it works....</p>
 536
 537                               <p class="entry-footer">
 538                                  <span class="post-footers">Posted by  at  7:04 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000632.html">Permalink</a>
 539
 540                                  | <a href="http://defaria.com/blogs/Status/archives/000632.html#trackback">TrackBacks (0)</a>
 541                               </p>
 542                            </div>
 543                         </div>
 544                      </div>
 545
 546                      <!--
 547 <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
 548          xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/"
 549          xmlns:dc="http://purl.org/dc/elements/1.1/">
 550 <rdf:Description
 551     rdf:about="http://defaria.com/blogs/Status/archives/2007_04.html#entry-000631"
 552     trackback:ping="http://defaria.com/mt/mt-tb.cgi/20"
 553     dc:title="Deleting Site Domains"
 554     dc:identifier="http://defaria.com/blogs/Status/archives/2007_04.html#entry-000631"
 555     dc:subject="Texas Instruments"
 556     dc:description=" Implemented gpdb_deleteSiteDomain..."
 557     dc:creator=""
 558     dc:date="2007-04-13T21:44:25-06:00" />
 559 </rdf:RDF>
 560 -->
 561
 562
 563                      <h2 class="date-header">April 13, 2007</h2>
 564                      <a id="a000631"></a>
 565                      <div class="entry" id="entry-631">
 566                         <h3 class="entry-header">Deleting Site Domains</h3>
 567                         <div class="entry-content">
 568                            <div class="entry-body">
 569                               <ul>
 570   <li>Implemented gpdb_deleteSiteDomain</li>
 571 </ul>
 572
 573                               <p>As we know, in GPDB there's very little in the realm of editing or validating of data. We've seen this with IP ranges where we let any old data in, including invalid IP ranges (let along the fact that the whole concept of IP ranges identifying sites is flawed to start with).</p>
 574
 575 <p>But as we can also see a site may have multiple domains (e.g. Dallas has many).</p>
 576
 577 <p>Site domains are implemented as their own table with the Site ID as the key and the "extended fields" of domain, IP range lower and upper being the data files.<p>
 578
 579 <div class=code><pre>
 580 -- site_domain_map: Table to map multiple domains to sites
 581 create table site_domain_map (
 582   id                number      (10)    not null,
 583   domain            varchar2    (256)   not null,
 584   ip_range_lower    varchar2    (15),
 585   ip_range_upper    varchar2    (15),
 586   foreign key (id) references sites (id)
 587 );
 588 </pre></div>
 589
 590 <p>But nothing stops the user or worse yet, a script, from adding more than one site domain that is exactly identical! So we can have, for example, two site domains for Dallas that have the domain name of "dal.design.ti.com".</p>
 591
 592 <p>As if that is not enough a real problem come when one attempts to delete. Let's say somebody added a second "dal.design.ti.com" Site Domain, notices the mistake and wants to delete the extra one.</p>
 593
 594 <p>Currently the code deletes site_domain_map entries using the following SQL statement:</p>
 595
 596 <div class=code><pre>
 597 DELETE FROM SITE_DOMAIN_MAP WHERE ID = 1000007 AND DOMAIN = 'dal.design.ti.com';
 598 </pre></div>
 599
 600 <p>This would delete both dal.design.ti.com entries, not just one.</p>
 601
 602 <p>I think the answer is to implement some validation such that people cannot add a second Site Domain of the same Domain name. Of course, this leaves the question is it considered legal to have two dal.design.ti.com Site Domains with different IP ranges. Which brings up the idea of validating not only a single IP range, but that no IP ranges overlap!</p>
 603
 604
 605                               <p class="entry-footer">
 606                                  <span class="post-footers">Posted by  at  9:44 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000631.html">Permalink</a>
 607
 608                                  | <a href="http://defaria.com/blogs/Status/archives/000631.html#trackback">TrackBacks (0)</a>
 609                               </p>
 610                            </div>
 611                         </div>
 612                      </div>
 613
 614                      <!--
 615 <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
 616          xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/"
 617          xmlns:dc="http://purl.org/dc/elements/1.1/">
 618 <rdf:Description
 619     rdf:about="http://defaria.com/blogs/Status/archives/2007_04.html#entry-000630"
 620     trackback:ping="http://defaria.com/mt/mt-tb.cgi/19"
 621     dc:title="testcc.pl"
 622     dc:identifier="http://defaria.com/blogs/Status/archives/2007_04.html#entry-000630"
 623     dc:subject="Texas Instruments"
 624     dc:description=" Created testcc.pl. This script creates a test vob, test view, makes elements, checks them in, out, modifies them, checks them in again and compares! Basic Clearcase sanity testing......"
 625     dc:creator=""
 626     dc:date="2007-04-10T17:53:20-06:00" />
 627 </rdf:RDF>
 628 -->
 629
 630
 631                      <h2 class="date-header">April 10, 2007</h2>
 632                      <a id="a000630"></a>
 633                      <div class="entry" id="entry-630">
 634                         <h3 class="entry-header">testcc.pl</h3>
 635                         <div class="entry-content">
 636                            <div class="entry-body">
 637                               <ul>
 638   <li>Created testcc.pl. This script creates a test vob, test view, makes elements, checks them in, out, modifies them, checks them in again and compares! Basic Clearcase sanity testing...</li>
 639 </ul>
 640
 641                               <p class="entry-footer">
 642                                  <span class="post-footers">Posted by  at  5:53 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000630.html">Permalink</a>
 643
 644                                  | <a href="http://defaria.com/blogs/Status/archives/000630.html#trackback">TrackBacks (0)</a>
 645                               </p>
 646                            </div>
 647                         </div>
 648                      </div>
 649
 650                      <!--
 651 <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
 652          xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/"
 653          xmlns:dc="http://purl.org/dc/elements/1.1/">
 654 <rdf:Description
 655     rdf:about="http://defaria.com/blogs/Status/archives/2007_04.html#entry-000629"
 656     trackback:ping="http://defaria.com/mt/mt-tb.cgi/18"
 657     dc:title="Convert Dallas/Licensing/Solaris 10 testing"
 658     dc:identifier="http://defaria.com/blogs/Status/archives/2007_04.html#entry-000629"
 659     dc:subject="Texas Instruments"
 660     dc:description=" Changed gpdb_convertuk.pl to open and use the new Dallas database cclic_report.pl reporting everybody as &quot;UNK&quot;. Tried to run this in debugger and it just worked! Hmmm... Is this a cron problem? Running again tonight Rick got the Jackson filer..."
 661     dc:creator=""
 662     dc:date="2007-04-09T19:23:36-06:00" />
 663 </rdf:RDF>
 664 -->
 665
 666
 667                      <h2 class="date-header">April  9, 2007</h2>
 668                      <a id="a000629"></a>
 669                      <div class="entry" id="entry-629">
 670                         <h3 class="entry-header">Convert Dallas/Licensing/Solaris 10 testing</h3>
 671                         <div class="entry-content">
 672                            <div class="entry-body">
 673                               <ul>
 674   <li>Changed gpdb_convertuk.pl to open and use the new Dallas database</li>
 675
 676   <li>cclic_report.pl reporting everybody as "UNK". Tried to run this in debugger and it just worked! Hmmm... Is this a cron problem? Running again tonight</li>
 677
 678   <li>Rick got the Jackson filer to mount to dslabcc01 however while I can create the vob storage area I cannot mount the vob!</li>
 679 </ul>
 680
 681                               <p class="entry-footer">
 682                                  <span class="post-footers">Posted by  at  7:23 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000629.html">Permalink</a>
 683
 684                                  | <a href="http://defaria.com/blogs/Status/archives/000629.html#trackback">TrackBacks (0)</a>
 685                               </p>
 686                            </div>
 687                         </div>
 688                      </div>
 689
 690                   </div>
 691                </div>
 692             </div>
 693          </div>
 694       </div>
 695    </div>
 696 </body>
 697 </html>