in Post- greSQL syntax; for example they can be used in expression operator ANY (subquery) con- structs, although an ESCAPE clause cannot be included there. In some obscure cases it may be neces- sary 3. Host Variables with Nonprimitive Types As a host variable you can also use arrays, typedefs, structs, and pointers. 33.4.4.3.1. Arrays There are two use cases for arrays as host variables. The first values; for example, take care to zero out any alignment padding bytes that might be present in structs. Without this, logically-equivalent constants of your data type might be seen as unequal by the planner

3. Host Variables with Nonprimitive Types As a host variable you can also use arrays, typedefs, structs, and pointers. 33.4.4.3.1. Arrays There are two use cases for arrays as host variables. The first values; for example, take care to zero out any alignment padding bytes that might be present in structs. Without this, logically-equivalent constants of your data type might be seen as unequal by the planner only plain old data structures (POD). This is necessary because backend errors generate a distant longjmp() that does not properly unroll a C++ call stack with non-POD objects. In summary, it is best

clause, or a row constructor. In all other contexts (including when nested inside one of those con- structs), attaching .* to a composite value does not change the value, since it means “all columns” and so 3. Host Variables with Nonprimitive Types As a host variable you can also use arrays, typedefs, structs, and pointers. 36.4.4.3.1. Arrays There are two use cases for arrays as host variables. The first values; for exam- ple, take care to zero out any alignment padding bytes that might be present in structs. Without this, logically-equivalent constants of your data type might be seen as unequal by the planner

in Post- greSQL syntax; for example they can be used in expression operator ANY (subquery) con- structs, although an ESCAPE clause cannot be included there. In some obscure cases it may be neces- sary 3. Host Variables with Nonprimitive Types As a host variable you can also use arrays, typedefs, structs, and pointers. 34.4.4.3.1. Arrays There are two use cases for arrays as host variables. The first values; for example, take care to zero out any alignment padding bytes that might be present in structs. Without this, logically-equivalent constants of your data type might be seen as unequal by the planner

33.6.3. Different types of host variables As a host variable you can also use arrays, typedefs, structs and pointers. Moreover there are special types of host variables that exist only in ECPG. A few values; for example, take care to zero out any alignment padding bytes that might be present in structs. Without this, logically-equivalent constants of your data type might be seen as unequal by the planner only plain old data structures (POD). This is necessary because backend errors generate a distant longjmp() that does not properly unroll a C++ call stack with non-POD objects. In summary, it is best

clause, or a row constructor. In all other contexts (including when nested inside one of those con- structs), attaching .* to a composite value does not change the value, since it means “all columns” and so 3. Host Variables with Nonprimitive Types As a host variable you can also use arrays, typedefs, structs, and pointers. 36.4.4.3.1. Arrays There are two use cases for arrays as host variables. The first values; for exam- ple, take care to zero out any alignment padding bytes that might be present in structs. Without this, logically-equivalent constants of your data type might be seen as unequal by the planner

clause, or a row constructor. In all other contexts (including when nested inside one of those con- structs), attaching .* to a composite value does not change the value, since it means “all columns” and so 3. Host Variables with Nonprimitive Types As a host variable you can also use arrays, typedefs, structs, and pointers. 36.4.4.3.1. Arrays There are two use cases for arrays as host variables. The first values; for exam- ple, take care to zero out any alignment padding bytes that might be present in structs. Without this, logically-equivalent constants of your data type might be seen as unequal by the planner

3. Host Variables with Nonprimitive Types As a host variable you can also use arrays, typedefs, structs, and pointers. 36.4.4.3.1. Arrays There are two use cases for arrays as host variables. The first values; for example, take care to zero out any alignment padding bytes that might be present in structs. Without this, logical- ly-equivalent constants of your data type might be seen as unequal by the only plain old data structures (POD). This is necessary because backend errors generate a distant longjmp() that does not properly unroll a C++ call stack with non-POD objects. In summary, it is best

3. Host Variables with Nonprimitive Types As a host variable you can also use arrays, typedefs, structs, and pointers. 33.4.4.3.1. Arrays There are two use cases for arrays as host variables. The first values; for example, take care to zero out any alignment padding bytes that might be present in structs. Without this, logically-equivalent constants of your data type might be seen as unequal by the planner only plain old data structures (POD). This is necessary because backend errors generate a distant longjmp() that does not properly unroll a C++ call stack with non-POD objects. In summary, it is best

3. Host Variables with Nonprimitive Types As a host variable you can also use arrays, typedefs, structs, and pointers. 33.4.4.3.1. Arrays There are two use cases for arrays as host variables. The first values; for example, take care to zero out any alignment padding bytes that might be present in structs. Without this, logically- equivalent constants of your data type might be seen as unequal by the only plain old data structures (POD). This is necessary because backend errors generate a distant longjmp() that does not properly unroll a C++ call stack with non-POD objects. In summary, it is best