|
1 | 1 | <!-- |
2 | | -$PostgreSQL: pgsql/doc/src/sgml/datatype.sgml,v 1.139 2003/12/21 04:34:35 momjian Exp $ |
| 2 | +$PostgreSQL: pgsql/doc/src/sgml/datatype.sgml,v 1.140 2004/01/20 22:46:06 tgl Exp $ |
3 | 3 | --> |
4 | 4 |
|
5 | 5 | <chapter id="datatype"> |
@@ -437,28 +437,6 @@ $PostgreSQL: pgsql/doc/src/sgml/datatype.sgml,v 1.139 2003/12/21 04:34:35 momjia |
437 | 437 | other <acronym>SQL</acronym> database systems. |
438 | 438 | </para> |
439 | 439 |
|
440 | | - <note> |
441 | | - <para> |
442 | | - If you have a column of type <type>smallint</type> or |
443 | | - <type>bigint</type> with an index, you may encounter problems |
444 | | - getting the system to use that index. For instance, a clause of |
445 | | - the form |
446 | | -<programlisting> |
447 | | -... WHERE smallint_column = 42 |
448 | | -</programlisting> |
449 | | - will not use an index, because the system assigns type |
450 | | - <type>integer</type> to the constant 42, and |
451 | | - <productname>PostgreSQL</productname> currently |
452 | | - cannot use an index when two different data types are involved. A |
453 | | - workaround is to single-quote the constant, thus: |
454 | | -<programlisting> |
455 | | -... WHERE smallint_column = '42' |
456 | | -</programlisting> |
457 | | - This will cause the system to delay type resolution and will |
458 | | - assign the right type to the constant. |
459 | | - </para> |
460 | | - </note> |
461 | | - |
462 | 440 | </sect2> |
463 | 441 |
|
464 | 442 | <sect2 id="datatype-numeric-decimal"> |
|