It was decided that DVD - while undoubtedly a good technical specification as such - is all too tightly controlled by DVD Consortium, a closed body of foreign companies. The political objectives of the Chinese government. This would be a huge market opportunity for anyone who could deliver the goods first. It was quite clear that at this high adoption rate, people would also be willing to purchase the 2nd generation video disc players (with better image quality and more features), once they should come available. The 1997 estimates ballooned to 18.20 million units. In 1995 there were less than 1 million hardware VCD players sold in China. The prevailing success of the original (White Book) Video CD format.
It all comes down to the following three reasons: First of all, why was there such a big interest in creating a new CD-based video disc format for China, at the time when the rest of the world was already preparing to accept DVD as the "next generation" digital video delivery format? The final SVCD spec, set by the China National Committee of Recording Standards, was announced in September 1998, winning out over C-Cube's China Video Disc (CVD) and HQ-VCD (from the developers of the original Video CD).Īs always, the background story is a bit more complicated than how it appears in brief summaries like the above. Table A-1.Super Video CD (aka SVCD, Super VCD or Chaoji VCD) is an enhancement to Video CD that was developed by a Chinese government-backed committee of manufacturers and researchers, partly to sidestep DVD technology royalties and partly to create pressure for lower DVD player and disc prices in China. As of PostgreSQL 9.3, complete coverage for this feature exists only for errors in SQLSTATE class 23 (integrity constraint violation), but this is likely to be expanded in future. Such names are supplied in separate fields of the error report message so that applications need not try to extract them from the possibly-localized human-readable text of the message. (Note that PL/pgSQL does not recognize warning, as opposed to error, condition names those are classes 00, 01, and 02.)įor some types of errors, the server reports the name of a database object (a table, table column, data type, or constraint) associated with the error for example, the name of the unique constraint that caused a unique_violation error. Condition names can be written in either upper or lower case.
The symbol shown in the column "Condition Name" is the condition name to use in PL/pgSQL.
SYSTRAN 6 INVALID CODE CODE
This code is used only for error conditions that fall within the class but do not have any more-specific code assigned. For each error class there is a "standard" error code having the last three characters 000. (Some are not actually used at present, but are defined by the SQL standard.) The error classes are also shown. Table A-1 lists all the error codes defined in PostgreSQL 9.6.24. Thus, an application that does not recognize the specific error code might still be able to infer what to do from the error class. Note that some, but not all, of the error codes produced by PostgreSQL are defined by the SQL standard some additional error codes for conditions not defined by the standard have been invented or borrowed from other databases.Īccording to the standard, the first two characters of an error code denote a class of errors, while the last three characters indicate a specific condition within that class. The error codes are less likely to change across PostgreSQL releases, and also are not subject to change due to localization of error messages. Applications that need to know which error condition has occurred should usually test the error code, rather than looking at the textual error message. All messages emitted by the PostgreSQL server are assigned five-character error codes that follow the SQL standard's conventions for "SQLSTATE" codes.
0 kommentar(er)
