@prefix rdf:	<http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix ns1:	<http://data.openlinksw.com/oplweb/product_category_feature/ResultsetHoldability#> .
@prefix OpenLink:	<http://www.openlinksw.com/schemas/oplweb#> .
ns1:this	rdf:type	OpenLink:ProductCategoryFeature .
@prefix rdfs:	<http://www.w3.org/2000/01/rdf-schema#> .
ns1:this	rdfs:label	"Resultset Holdability" ;
	OpenLink:Description	"Resultset Holdability" .
@prefix ns4:	<http://data.openlinksw.com/oplweb/product_benefit/SophisticatedApplicationFunctionality#> .
ns1:this	OpenLink:isOfProductBenefit	ns4:this .
@prefix ns5:	<http://data.openlinksw.com/oplweb/product_feature_category/StandardsCompliance#> .
ns1:this	OpenLink:isOfProductFeatureCategory	ns5:this .
@prefix ns6:	<http://data.openlinksw.com/oplweb/product_category/jdbc#> .
ns1:this	OpenLink:isOfProductCategory	ns6:this .
@prefix ns7:	<http://purl.org/dc/terms#> .
ns1:this	ns7:description	"A holdable cursor, or result, is one that does not automatically close when the transaction that contains the cursor is committed. JDBC 3.0 adds support for specifying cursor holdability. To specify the holdability of your ResultSet, you must do so when preparing a statement using the createStatement(), prepareStatement(), or prepareCall() methods. The holdability may be one of the following constants: HOLD_CURSORS_OVER_COMMIT or CLOSE_CURSORS_AT_COMMIT. Note it is more efficient to close CURSOR at the end of transactions (after the COMMIT). JDBC doesn't specifiy a default HOLD_CURSOR behavour but for resource expediency we have chosen CLOSE_CURSORS_AT_COMMIT as the default." ;
	OpenLink:isFeatureOf	ns6:this .
@prefix opl:	<http://www.openlinksw.com/schema/attribution#> .
ns1:this	opl:isDescribedUsing	rdfs: ,
		ns7: ,
		OpenLink: .