Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prepared statement [moved] #49

Closed
lvca opened this issue Dec 10, 2012 · 0 comments
Closed

Prepared statement [moved] #49

lvca opened this issue Dec 10, 2012 · 0 comments

Comments

@lvca
Copy link
Member

lvca commented Dec 10, 2012

This is Issue 49 moved from a Google Code project.
Added by 2010-06-23T10:26:00.000Z by l.garu...@gmail.com.
Please review that bug for more context and additional comments, but update this bug.
Closed (Fixed).

Original labels: Type-Enhancement, Priority-High, v0.9.25

Original description

OrientDB could support prepared statement using both SQL and JPA syntaxes.

Example of JPA syntax:

q = new OSQLSyncQuery( "SELECT FROM profile WHERE name = :name AND id = :id" );

args = new HashMap<String,Object>();
args.put( &quot;name&quot;, &quot;Jay&quot;);
args.put( &quot;id&quot;, 10 );

q.execute(args);

Example of SQL syntax:

q = new OSQLSyncQuery( &quot;SELECT FROM profile WHERE name = ? AND id = ?&quot;);
q.execute(&quot;Jay&quot;, 10);
@lvca lvca closed this as completed Dec 10, 2012
robfrank pushed a commit that referenced this issue Oct 15, 2015
lvca added a commit that referenced this issue Oct 15, 2015
robfrank pushed a commit that referenced this issue Oct 15, 2015
release plugin configuration
tglman pushed a commit that referenced this issue Feb 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant