Been Busy... and some Oracle .Net Provider goodies.
It's seems as though I've had no free time as of late. Between work, sleep and more work I haven't had time for bloggin'. Though thanks to NewsGator, I've been able to keep up with everyone else.
Over the weekend, I picked up a Sony DRX-500UL drive from Best Buy. So far it's been great!! I'm currently clearing up my MP3 collection up and backing up some important files.
So for the past week I've been working on a project that uses the Oracle .Net Provider from Oracle. I picked this one over Microsoft's implementation after some test runs that yielded about 10 to 30 secs faster data access on Oracle's side. This is above the 120% speed increase I got when moving from OleDB to Microsoft's Oracle Provider. Luckily if down the road Microsoft's gets faster the Naming conventions are almost identical.
Along with messing with the Oracle Provider I've started porting over MS's Data Access Block to use Oracle, which I will post this week. For those of you that haven't used the Data Access Block from Microsoft, you should. For a simple data access layer nothing beats it really. you can check this block and the other ones here.
So doing something similiar to the SQL Data Access stuff you get something like this:
Dim odr As OracleDataReader
Dim oraparams() As OracleParameter = New OracleParameter(1) {}
oraparams(0) = New OracleParameter("TERM_IN", OracleDbType.Varchar2)
oraparams(0).Value = sSearch
oraparams(1) = New OracleParameter("THE_NAMES", OracleDbType.RefCursor, ParameterDirection.Output)
oraparams(1).Value = Nothing
Try
odr = ODF.ExecuteReader("...", commandType.StoredProcedure, "SEARCH_SIMPLE_NAME", oraparams)
TextSearchGrid.DataSource = odr
TextSearchGrid.DataBind()
TextSearchGrid.Visible = True
TextSearchLabel.Visible = True
Catch oe As OracleException
' don't do anything.
End Try
Real simple right? Notice the last parameter, this is for the REF_CURSOR that is returned. There are a few different ways of returning a REF_CURSOR, this one being the easiest.