Comments on: ruby-plsql 0.4.1 – support for package variables, views, dbms_output and more http://blog.rayapps.com/2010/01/04/ruby-plsql-0-4-1-support-for-package-variables-views-dbms_output-and-more/ About Ruby, Oracle, Mac and others Wed, 28 Jul 2010 16:18:03 +0000 hourly 1 http://wordpress.com/ By: Martin http://blog.rayapps.com/2010/01/04/ruby-plsql-0-4-1-support-for-package-variables-views-dbms_output-and-more/#comment-1121 Martin Fri, 19 Feb 2010 12:38:02 +0000 http://rayapps.wordpress.com/?p=131#comment-1121 I'm using ruby-plsql with rails. When putting require 'ruby-plsql' plsql.activerecord_class = ActiveRecord::Base plsql.connection.autocommit = false at the end of environment.db, I could not start webrick anymore. Wenn putting the same statements in front of a class models/plsql_processor.rb, I have no problems, everything works. Any ideas what the best place to put these statements is? Seems to depend on rails' initialization progress... I’m using ruby-plsql with rails. When putting

require ‘ruby-plsql’
plsql.activerecord_class = ActiveRecord::Base
plsql.connection.autocommit = false

at the end of environment.db, I could not start webrick anymore.
Wenn putting the same statements in front of a
class models/plsql_processor.rb, I have no problems, everything works.

Any ideas what the best place to put these statements is? Seems to depend
on rails’ initialization progress…

]]> By: Raimonds Simanovskis http://blog.rayapps.com/2010/01/04/ruby-plsql-0-4-1-support-for-package-variables-views-dbms_output-and-more/#comment-1087 Raimonds Simanovskis Sun, 17 Jan 2010 21:45:41 +0000 http://rayapps.wordpress.com/?p=131#comment-1087 Currently VARCHAR2(n CHAR) type is not supported - I am parsing all_source data dictionary view to find out variable definitions and didn't include pattern for recognizing CHAR modifier for VARCHAR2 length. I will fix it in next version of ruby-plsql. Currently VARCHAR2(n CHAR) type is not supported – I am parsing all_source data dictionary view to find out variable definitions and didn’t include pattern for recognizing CHAR modifier for VARCHAR2 length. I will fix it in next version of ruby-plsql.

]]> By: GZI http://blog.rayapps.com/2010/01/04/ruby-plsql-0-4-1-support-for-package-variables-views-dbms_output-and-more/#comment-1082 GZI Wed, 13 Jan 2010 12:36:14 +0000 http://rayapps.wordpress.com/?p=131#comment-1082 Is there any specific code to access global package variable defined as VARCHAR2(50 CHAR)? CREATE OR REPLACE PACKAGE test_package IS varchar2_variable VARCHAR2(50); varchar2char_variable VARCHAR2(50 CHAR); END; plsql.test_package.varchar2_variable = 'test' -- OK plsql.test_package.varchar2char_variable = 'test' -- NOK (No PL/SQL procedure or variable 'varchar2char_variable' found) Is there any specific code to access global package variable defined as VARCHAR2(50 CHAR)?

CREATE OR REPLACE PACKAGE test_package IS
varchar2_variable VARCHAR2(50);
varchar2char_variable VARCHAR2(50 CHAR);
END;

plsql.test_package.varchar2_variable = ‘test’ — OK
plsql.test_package.varchar2char_variable = ‘test’ — NOK (No PL/SQL procedure or variable ‘varchar2char_variable’ found)

]]> By: Raimonds Simanovskis http://blog.rayapps.com/2010/01/04/ruby-plsql-0-4-1-support-for-package-variables-views-dbms_output-and-more/#comment-1080 Raimonds Simanovskis Tue, 05 Jan 2010 09:28:28 +0000 http://rayapps.wordpress.com/?p=131#comment-1080 Found out that underlying ruby-oci8 library (OCI wrapper in Ruby) that I use in ruby-plsql already provides interface for that - http://limlian.blogspot.com/2008/05/ruby-oci8-v20-new-feature-array-dml.html Found out that underlying ruby-oci8 library (OCI wrapper in Ruby) that I use in ruby-plsql already provides interface for that – http://limlian.blogspot.com/2008/05/ruby-oci8-v20-new-feature-array-dml.html

]]> By: Raimonds Simanovskis http://blog.rayapps.com/2010/01/04/ruby-plsql-0-4-1-support-for-package-variables-views-dbms_output-and-more/#comment-1079 Raimonds Simanovskis Tue, 05 Jan 2010 09:02:11 +0000 http://rayapps.wordpress.com/?p=131#comment-1079 Yes, ruby-oci8 2.0.3 core features are as stable as in ruby-oci8 1.x, there are just some bugs in new complex data type support features. I plan to support just ruby-oci8 2.0.3 or later in future ruby-plsql and oracle_enhanced versions as I start to use many ruby-oci8 2.x features and it is too complicated to maintain backwards compatibility with ruby-oci8 1.x :) Yes, ruby-oci8 2.0.3 core features are as stable as in ruby-oci8 1.x, there are just some bugs in new complex data type support features. I plan to support just ruby-oci8 2.0.3 or later in future ruby-plsql and oracle_enhanced versions as I start to use many ruby-oci8 2.x features and it is too complicated to maintain backwards compatibility with ruby-oci8 1.x :)

]]> By: DeLynn Berry http://blog.rayapps.com/2010/01/04/ruby-plsql-0-4-1-support-for-package-variables-views-dbms_output-and-more/#comment-1078 DeLynn Berry Tue, 05 Jan 2010 06:30:14 +0000 http://rayapps.wordpress.com/?p=131#comment-1078 Looks like another great release Raimonds! I've held off upgrading to these newer versions because of the OCI8 > v2.0 dependency. I haven't seen anything from the OCI8 developer to suggest that the 2.0 line is production ready. I can only assume though that you are using it very regularly. Do you feel like the 2.0 library is as production ready as the existing 1.0 product? Looks like another great release Raimonds! I’ve held off upgrading to these newer versions because of the OCI8 > v2.0 dependency. I haven’t seen anything from the OCI8 developer to suggest that the 2.0 line is production ready. I can only assume though that you are using it very regularly. Do you feel like the 2.0 library is as production ready as the existing 1.0 product?

]]> By: Cary Millsap http://blog.rayapps.com/2010/01/04/ruby-plsql-0-4-1-support-for-package-variables-views-dbms_output-and-more/#comment-1077 Cary Millsap Tue, 05 Jan 2010 01:11:36 +0000 http://rayapps.wordpress.com/?p=131#comment-1077 P.S.: Please don't overlook the end-to-end diagnostics features of the OCI that allow application developers using your drivers to instrument their code. When developers can instrument code paths with service, module, action, and client information (exposed as OCI_ATTR_SERVICE, OCI_ATTR_MODULE, OCI_ATTR_ACTION, OCI_ATTR_CLIENT_IDENTIFIER, OCI_ATTR_CLIENT_INFO, etc. in the OCI model), then they have a *much* easier time measuring and improving the performance of their applications throughout the software life cycle. Cary P.S.: Please don’t overlook the end-to-end diagnostics features of the OCI that allow application developers using your drivers to instrument their code. When developers can instrument code paths with service, module, action, and client information (exposed as OCI_ATTR_SERVICE, OCI_ATTR_MODULE, OCI_ATTR_ACTION, OCI_ATTR_CLIENT_IDENTIFIER, OCI_ATTR_CLIENT_INFO, etc. in the OCI model), then they have a *much* easier time measuring and improving the performance of their applications throughout the software life cycle.

Cary

]]> By: Cary Millsap http://blog.rayapps.com/2010/01/04/ruby-plsql-0-4-1-support-for-package-variables-views-dbms_output-and-more/#comment-1076 Cary Millsap Tue, 05 Jan 2010 00:58:45 +0000 http://rayapps.wordpress.com/?p=131#comment-1076 It's good that you're going to attend to it. You won't have a problem finding the OCI support for what you're looking for. Search http://download.oracle.com/docs/cd/E11882_01/appdev.112/e10646/oci04sql.htm#g454129 for the string "Batch Error Mode" for part of what you'll need. Good luck! Cary It’s good that you’re going to attend to it.

You won’t have a problem finding the OCI support for what you’re looking for. Search http://download.oracle.com/docs/cd/E11882_01/appdev.112/e10646/oci04sql.htm#g454129 for the string “Batch Error Mode” for part of what you’ll need.

Good luck!

Cary

]]> By: Raimonds Simanovskis http://blog.rayapps.com/2010/01/04/ruby-plsql-0-4-1-support-for-package-variables-views-dbms_output-and-more/#comment-1075 Raimonds Simanovskis Mon, 04 Jan 2010 23:42:11 +0000 http://rayapps.wordpress.com/?p=131#comment-1075 Actually currently insert_values will create a separate prepared statement for each row - so probably I will improve it in future to use just of prepared statement to enhance performance for insertion of many rows. In this case I could also use setExecuteBatch JDBC method to reduce network roundtrips (need to find if I can do something similar using OCI C library as well). So thanks for bringing my attention to it :) Actually currently insert_values will create a separate prepared statement for each row – so probably I will improve it in future to use just of prepared statement to enhance performance for insertion of many rows. In this case I could also use setExecuteBatch JDBC method to reduce network roundtrips (need to find if I can do something similar using OCI C library as well). So thanks for bringing my attention to it :)

]]> By: Raimonds Simanovskis http://blog.rayapps.com/2010/01/04/ruby-plsql-0-4-1-support-for-package-variables-views-dbms_output-and-more/#comment-1074 Raimonds Simanovskis Mon, 04 Jan 2010 23:25:16 +0000 http://rayapps.wordpress.com/?p=131#comment-1074 1. It will perform two distinct INSERT INTO statements. As currently it is mostly meant for unit test data preparation I do not worry too much about network latency. When you will run your tests in continuous integration then anyway it is preferred to run it from machine which have fast network connection to database. 2. ruby-plsql will use bind variables with prepared cursor both for table/view operations as well as for procedure calls with parameters. (It has different implementation compared to ActiveRecord oracle_enhanced adapter which always generates all variables inside SQL string as literals - but that's different topic). 1. It will perform two distinct INSERT INTO statements. As currently it is mostly meant for unit test data preparation I do not worry too much about network latency. When you will run your tests in continuous integration then anyway it is preferred to run it from machine which have fast network connection to database.

2. ruby-plsql will use bind variables with prepared cursor both for table/view operations as well as for procedure calls with parameters. (It has different implementation compared to ActiveRecord oracle_enhanced adapter which always generates all variables inside SQL string as literals – but that’s different topic).

]]>