08-20-2013
The tty may be cooking up some binary input, but this is far short of handlong nulls -- they just passed through. Bash did not detect them as null.
4 More Discussions You Might Find Interesting
1. Programming
how about asynchronous canceling?
or with signal?
if with signal whether it effects the process?
my english so badly :( :( (1 Reply)
Discussion started by: alan.zhao
1 Replies
2. Shell Programming and Scripting
Hello *nix specialists,
Im working for a non profit organisation in Germany to transport DSL over WLAN to people in areas without no DSL. We are using Linksys WRT 54 router with DD-WRT firmware There are at the moment over 180 router running but we have to change some settings next time. So my... (7 Replies)
Discussion started by: digidax
7 Replies
3. Shell Programming and Scripting
Apologies for any typos, and IF this has been done before...
This is yet another building block. The code generates a 256 byte binary file of _characters_ 0x00 to 0xFF for general usage and generates another binary file manipulated in a basic way.
I need this facility for a kids project I am... (0 Replies)
Discussion started by: wisecracker
0 Replies
4. Forum Support Area for Unregistered Users & Account Problems
Dear Moderator
I am not able to post any new thread or post reply to mine old thread.
Kindly help as i am stuck on one problem and needed suggestion.
Regards
Jaydeep (1 Reply)
Discussion started by: jaydeep_sadaria
1 Replies
LEARN ABOUT CENTOS
spi_execute_plan
SPI_EXECUTE_PLAN(3) PostgreSQL 9.2.7 Documentation SPI_EXECUTE_PLAN(3)
NAME
SPI_execute_plan - execute a statement prepared by SPI_prepare
SYNOPSIS
int SPI_execute_plan(SPIPlanPtr plan, Datum * values, const char * nulls,
bool read_only, long count)
DESCRIPTION
SPI_execute_plan executes a statement prepared by SPI_prepare or one of its siblings. read_only and count have the same interpretation as
in SPI_execute.
ARGUMENTS
SPIPlanPtr plan
prepared statement (returned by SPI_prepare)
Datum * values
An array of actual parameter values. Must have same length as the statement's number of arguments.
const char * nulls
An array describing which parameters are null. Must have same length as the statement's number of arguments. n indicates a null value
(entry in values will be ignored); a space indicates a nonnull value (entry in values is valid).
If nulls is NULL then SPI_execute_plan assumes that no parameters are null.
bool read_only
true for read-only execution
long count
maximum number of rows to return, or 0 for no limit
RETURN VALUE
The return value is the same as for SPI_execute, with the following additional possible error (negative) results:
SPI_ERROR_ARGUMENT
if plan is NULL or invalid, or count is less than 0
SPI_ERROR_PARAM
if values is NULL and plan was prepared with some parameters
SPI_processed and SPI_tuptable are set as in SPI_execute if successful.
PostgreSQL 9.2.7 2014-02-17 SPI_EXECUTE_PLAN(3)