sybase_unbuffered_query Send a Sybase query and do not block &reftitle.description; resourcesybase_unbuffered_query stringquery resourcelink_identifier boolstore_result sybase_unbuffered_query sends a query to the currently active database on the server that's associated with the specified link identifier. If the link identifier isn't specified, the last opened link is assumed. If no link is open, the function tries to establish a link as if sybase_connect was called, and use it. Unlike sybase_query, sybase_unbuffered_query reads only the first row of the result set. sybase_fetch_array and similar function read more rows as needed. sybase_data_seek reads up to the target row. The behavior may produce better performance for large result sets. sybase_num_rows will only return the correct number of rows if all result sets have been read. To Sybase, the number of rows is not known and is therefore computed by the client implementation. If you don't read all of the resultsets prior to executing the next query, PHP will raise a warning and cancel all of the pending results. To get rid of this, use sybase_free_result which will cancel pending results of an unbuffered query. &reftitle.parameters; query link_identifier store_result The optional store_result can be &false; to indicate the resultsets shouldn't be fetched into memory, thus minimizing memory usage which is particularly interesting with very large resultsets. &reftitle.returnvalues; Returns a positive Sybase result identifier on success, or &false; on error. &reftitle.examples; '; if ($i++ > 40000) { break; } } sybase_free_result($q); sybase_close($dbh); ?> ]]> &reftitle.notes; &sybase.ct.only; &reftitle.seealso; sybase_query