codemonth blog codemonth blog - One project every month - making stuff better. Sun, 23 Apr 2017 17:30:59 +0700 Sun, 23 Apr 2017 17:30:59 +0700 30 Completing JWT_NINjA for full JWT support 4CBC2BC376CF83D6E050007F01003814 Sun, 09 Apr 2017 09:08:11 +0700 <p>In the single <a href="">blog post</a> I wrote on the JWT_NINJA package back in June last year, I ended the post by saying that I needed to implement both a verify and a parse function for the package.</p><p>Well, it took me a year, but I finally had a reason to go and implement it. As I am getting into Oracle ORDS and trying to get some experience in building REST services, I want to be able to use <a href="">JWT</a> as the token generator for the application that I am building.</p><p>So a quick refresh on how to generate a token using the package:</p> <pre><code class="language-sql"> select jwt_ninja.jwt_generate(p_signature_key => 'my secret password', p_reg_claim_issuer => 'My Application', p_reg_claim_subject => '147654') as token from dual; TOKEN ------------------------------------------------------------------------------------------------------------------------------------- eyAiYWxnIjogIkhTMjU2IiwgInR5cCI6ICJKV1QiIH0.eyAiaWF0IjogMTQ5MTcxNzIxODAwMCwgImlzcyI6ICJNeSBBcHBsaWNhdGlvbiIs ICJzdWIiOiAiMTQ3NjU0In0.Uy6KeKeO1/52+URTbhk1+spOIO3OYamLhViPJ1ZmjUU </code></pre> <p>So now that we have a token, we would store that on the client side, and every request from the client would include this token for us to validate. So to validate the token there is now a procedure jwt_ninja.jwt_verify_and_decode that will do just that. The third argument (p_do_parse) indicates if you only want the token to be verified or if you want to parse the fields inside the payload. The default is to only verify the validity of the signature and the message and not do the parse. If it is set to true, the values of the different <a href="">JWT claims</a> will be set and found in the output parameters of the procedure.</p><p> <pre><code class="language-sql"> declare mysecret varchar2(4000) := 'my secret password'; mytoken varchar2(4000) := jwt_ninja.jwt_generate(p_signature_key => 'my secret password', p_reg_claim_issuer => 'My Application', p_reg_claim_subject => '147654'); doparse boolean := false; myresult boolean; l_reg_claim_issuer varchar2(4000) := null; l_reg_claim_subject varchar2(4000) := null; l_reg_claim_audience varchar2(4000) := null; l_reg_claim_expiration date := null; l_reg_claim_notbefore date := null; l_reg_claim_issuedat date := null; l_reg_claim_jwtid varchar2(4000) := null; begin jwt_ninja.jwt_verify_and_decode(mytoken, mysecret, doparse, myresult, l_reg_claim_issuer, l_reg_claim_subject, l_reg_claim_audience, l_reg_claim_expiration, l_reg_claim_notbefore, l_reg_claim_issuedat, l_reg_claim_jwtid); if myresult then dbms_output.put_line('Verified'); dbms_output.put_line('Iss: ' || l_reg_claim_issuer); dbms_output.put_line('Sub: ' || l_reg_claim_subject); else dbms_output.put_line('Not verified'); end if; end; / </code></pre></p> <p>So know I can "close" this codemonth for now, since I can start to use it in my other project.</p> Take a random REST 4CA6C3C984F556E6E050007F01006CD5 Sat, 08 Apr 2017 10:07:37 +0700 <p>I needed to test <a href="">ORDS</a> for some webservice related projects at work. So I decided to build a rest interface for all the different random data functions in the <a href="">RANDOM_NINJA</a> package to test out, just how easy it is.</p><p>First order is to setup ORDS. Like always Tim over at <a href="">oracle-base</a> have a couple of really good articles on installing and setting up ORDS itself. So no need for me to duplicate that.</p><p>After setting up ORDS, and enabling my schema for rest services like in this <a href="">oracle-base article</a>, it is time to enable the functions in the different data domain packages. I decided to keep the URL scheme simple, so that the path would be /[package_name]/[function_name]/ for any of the functions that are part of the RANDOM_NINJA package.</p> Generating randomized incremental values 4AB10279DD66941AE050007F01003083 Tue, 14 Mar 2017 10:35:06 +0700 <p>In the previous entries, I explained the <a href="">basics of testdata_ninja</a> and then I explained how to <a href="">create foreign key relations</a> between your test data and existing tables. This time I will show how you can create data that are random but always increasing, either to create time patterns or to create unique id columns for primary keys. I will extend the format that I have already used in the previous entries, so the code will be familiar. If we look at the output of the test_days generator we have created, it currently looks like this: <pre><code class="language-sql"> SQL> select * from table(tdg_test_days.test_days); NAME BIRTHDAY MY_PK_REF -------------------------------------------------- ------------------ ---------- Arianna Turner 02-MAR-93 00:24:58 1 Sofie Dam 17-MAY-91 17:21:09 1 Camila King 27-OCT-62 18:16:56 10 Malik Henriksen 24-NOV-65 06:23:51 10 .... [more rows] .... </code></pre> There is no clear column with possible unique values, so I will create a new column where the data generator is an "incrementor". Like all the other different data fields, it is in the 3 field definition of the block that we define how to generate the data. So far the format looks like this: <pre><code class="language-sql"> name#varchar2(50)#person_random.r_name@birthday#date#person_random.r_birthday@my_pk_ref#number#£t_people¤person_num_pk¤simple¤5 </code></pre> So let us add a column in the beginning, that increments randomly but is unique nonetheless: <pre><code class="language-sql"> people_pk#number#^numiterate~1~3¤5 </code></pre> and here is the explanation of the fields, which are separated by the "~" character: <ul> <li>incrementor type (numiterate for numbers and datiterate for dates)</li> <li>start from (number or date to start increment from)</li> <li>increment range (for numbers min and max separated by the "¤" character and dates interval type (seconds, minutes etc), min and max separated by the "¤" character for example: seconds¤1¤5)</li> </ul> So if we now take a look at the full format in the code, it would look like this: <pre><code class="language-sql"> declare the_format varchar2(4000) := 'people_pk#number#^numiterate~1~3¤5@name#varchar2(50)#person_random.r_name@birthday#date#person_random.r_birthday@my_pk_ref#number#£t_people¤person_num_pk¤simple¤5'; begin testdata_ninja.generator_create('test_days', the_format); end; / </code></pre> And would create a result like the following: <pre><code class="language-sql"> 1 Sigurd Andreasen 20-NOV-63 12:33:49 1 6 Ella Madsen 30-JAN-80 07:09:39 1 9 Alexandra White 16-JUL-53 16:32:07 1 13 Benjamin Holst 08-APR-88 13:39:38 1 17 Lea Jepsen 24-MAY-88 17:21:01 1 21 Eli Morgan 07-AUG-86 15:54:27 10 26 Oskar Bruun 20-JUL-69 22:40:56 10 31 Jens Friis 26-APR-63 16:32:21 10 35 Camila Hall 05-DEC-78 23:30:19 10 </code></pre> Test data and foreign keys 4A9DA728FCF0404EE050007F010074D7 Mon, 13 Mar 2017 10:16:59 +0700 In my <a href="">last entry</a> on testdata_ninja I showed the basics on how to create your own custom test data generators.</p><p>Once you have created the simple ones you probably want to extend it a little bit, and create test tables that has relations. So you want to create random data, but random data that actually can join to another table. The way to do this, is with a special data generator construct in the testdata_ninja format. If you read the old entry, you can see that testdata_ninja format is a series of columns seperated by the "@" sign. Each column has at least 3 parts (divided by the "#" character), where the third is the data generator.</p><p>So in the previous example I wrote about we used functions from the <a href="">random_ninja</a> package. You can however, reference existing tables instead. First we want to create a master table that we can reference in our new generator. We will use the basic data generators that are already part of the testdata_ninja package to create this: <pre><code class="language-sql"> create table t_people as select * from table(testdata_generator.people(100)); </code></pre> This statement will create a table with a hundred rows in. This table is what we will use to create our other test data table. One of the rows is called person_num_pk, and that is the column with the relation to our other table. The way we define that is with a special character as the first character in our generator field. So in my last entry I defined the test table with the following format: <pre><code class="language-sql"> name#varchar2(50)#person_random.r_name@birthday#date#person_random.r_birthday </code></pre> So let us say that I wanted to add another column here, that linked to my primary key in the new table I just created. If I wanted to do that I simply create a third column definition like the following: <pre><code class="language-sql"> name#varchar2(50)#person_random.r_name@birthday#date#person_random.r_birthday@my_pk_ref#number#£t_people¤person_num_pk¤simple¤5 </code></pre> Notice the "£" sign. This is what specifies this generator as a reference to another table and not a function. The fields in the reference generator (divided with the "¤" character) are the following:</p><p> <ul> <li>table name that we are referencing (t_people)</li> <li>column in that table we are referencing (person_num_pk)</li> <li>distribution rule (simple or range)</li> <li>distribution count. If simple just one number, and every ref will this many rows in the new generator or range and you specify 2,5 then every reference will have between 2 and 5 rows in the new generator</li> </ul> So to create this new table we would simply run: <pre><code class="language-sql"> declare the_format varchar2(4000) := 'name#varchar2(50)#person_random.r_name@birthday#date#person_random.r_birthday@my_pk_ref#number#£t_people¤person_num_pk¤simple¤5'; begin testdata_ninja.generator_create('test_days', the_format); end; / </code></pre> and we can now select from the generator and see that each value in the my_pk_ref column will be a real reference back to the t_people table and there will be 5 "child" rows per real row from the t_people table: <pre><code class="language-sql"> select a.first_name , b.birthday from t_people a , (select name, birthday, my_pk_ref from table(tdg_test_days.test_days)) b where a.person_num_pk = b.my_pk_ref; FIRST_NAME BIRTHDAY ---------------------------------------------------------------------------------------------------- ------------------ Parker 14-SEP-64 13:35:56 Parker 18-APR-62 05:02:35 Parker 05-SEP-93 12:35:50 Parker 16-AUG-82 21:19:14 Parker 11-MAR-85 15:51:54 Bryson 03-SEP-84 19:56:20 Bryson 08-JUL-96 14:33:07 Bryson 30-DEC-62 06:28:59 .......... [more rows] </code></pre> Creating real test data - Fast and Efficiently 4A88304CCF5766B8E050007F01004878 Sun, 12 Mar 2017 09:10:18 +0700 <p>When I build <a href="">RANDOM_NINJA</a> I knew already one of things I wanted to use that library for. Building good valid and life-like test data has and is always a really big problem. The base for good test data is good and valid looking random data. Without that, most tests are not really valid, as data can be clustered wrongly, indexes act strange because data does not mimic real life and relations and constraints are hard to define or validate on data that is created using most available randomizing packages. That is why it was important to me that <a href="">RANDOM_NINJA</a> would be able to create random data from as many different domains as possible. As of today it can create more than 185 different data points from as many as 14 different data domains.</p><p>But having good random data is only half of it. You still need something that can define and create those tables. You also need something that can still maintain relations between those test tables, and make sure that foreign key distributions are real as well. So I created <a href="">TESTDATA_NINJA</a>. This package has some generic generators to create simple tables of people, <a href="">populations</a> which are true according to UN demographics data, CDR records and credit card transactions. The real function in this package is the custom generation procedure. This procedure can parse a string representation of what your data looks like and from that create pipelined functiones that can create thousands of test rows extremely fast and efficiently.</p><p>The testdata_ninja.generator_create procedure takes 2 arguments. The name of the new generator and the format of the test data. Below is a short description on how the format looks like.</p> plsql promises - promise complete solution 495B501DA98CB9A8E050007F0100141E Sat, 25 Feb 2017 08:28:28 +0700 <p>Finally. I got the 2 last methods completed. promise.all and promise.race is finished. So now the plsql promises library is feature complete. <b>promise.all</b> method takes a list of promises, built with the help of the <b>promises_ninja</b> package, and once the entire list of promises is fulfilled the top promise is set to fulfilled. Here is an example:</p> <p><pre><code class="language-sql">-- Test all method declare test_promise promise := promise(); a_promise1 promise; a_promise2 promise; a_promise3 promise; all_promises promises_ninja.promise_list_type; begin a_promise1 := promise('p_multiplier', 10); promises_ninja.build_promise_list(all_promises, a_promise1); a_promise2 := promise('p_multiplier', 20); promises_ninja.build_promise_list(all_promises, a_promise2); a_promise3 := promise('p_multiplier', 30); promises_ninja.build_promise_list(all_promises, a_promise3); test_promise.all_p(promises_ninja.convert_promise_list(all_promises)); dbms_lock.sleep(5); test_promise.check_and_set_value(); dbms_output.put_line('State is: ' || test_promise.state); end; /</code></pre></p><p>The output is the list of the promises with the fulfilled values. So you can loop through the output and display individual values like this:</p> <p><pre><code class="language-sql">declare test_promise promise := promise(); a_promise1 promise; a_promise2 promise; a_promise3 promise; all_promises promises_ninja.promise_list_type; promise_list_o promises_list_obj; promise_val promise; begin a_promise1 := promise('p_multiplier', 10); promises_ninja.build_promise_list(all_promises, a_promise1); a_promise2 := promise('p_multiplier', 20); promises_ninja.build_promise_list(all_promises, a_promise2); a_promise3 := promise('p_multiplier', 30); promises_ninja.build_promise_list(all_promises, a_promise3); test_promise.all_p(promises_ninja.convert_promise_list(all_promises)); dbms_lock.sleep(5); test_promise.check_and_set_value(); dbms_output.put_line('State is: ' || test_promise.state); if test_promise.val.getObject(promise_list_o) = dbms_types.success then -- We converted the object successfully for i in 1..promise_list_o.promise_list.count loop if promise_list_o.promise_list(i).getObject(promise_val) = dbms_types.success then -- We have an individual promise output value dbms_output.put_line('Value of promise is: ' || promise_val.getanyvalue); end if; end loop; end if; end; /</code></pre></p><p>Same code and technique can be used for the race method. The only difference is that the output in the race call is a normal promise and not a list of promises, as only the first promise to complete is returned.</p> Updated random_ninja and testdata_ninja packages 48C7A67F9002EA7AE050007F010061CE Sat, 18 Feb 2017 04:47:39 +0700 <p>A couple of people have requested that I explain how to install the entire random_ninja and testdata_ninja packages manually. I have created a gist here with the full and complete order of the files: <a href="">Full install list</a>. So download <a href="">random_ninja zipfile</a> and <a href="">testdata_ninja zipfile</a> and follow the order of the gist to install all the code.</p> <p>Once you have installed the packages you have the full random library available, which you can read in full detail about here: <a href="">Post #1</a>, <a href="">Post #2</a> and <a href="">Post #3</a>. For testdata package you can see a quick demo <a href="">here</a> and <a href="">here</a>.</p> <p>Release 3 of random_ninja is coming up and this is the list of new functionality that will be fully supported (HINT: The code is already in the github source): <ul> <li><strong>company_random</strong> <ul> <li><strong>r_companyname</strong> - generate a random company name.</li> <li><strong>r_industry</strong> - generate a random industry type.</li> <li><strong>r_companyid</strong> - generate a random country tax id.</li> <li><strong>r_employees</strong> - generate a random employee count.</li> <li><strong>r_revenue</strong> - generate a random revenue number.</li> </ul> </li> <li><strong>phone_random</strong> <ul> <li><strong>r_brand</strong> - generate a random brand name.</li> </ul> </li> <li><strong>computer_random</strong> <ul> <li><strong>r_error</strong> - generate a random error string.</li> </ul> </li> <li><strong>util_random</strong> <ul> <li><strong>ru_permute</strong> - Permute a string: Morten -> Metron.</li> <li><strong>ru_scramble</strong> - Scramble a string: Morten -> Diwnah.</li> <li><strong>ru_obfuscate</strong> - Obfuscate a string: Morten -> FasNituha.</li> </ul> </li> <li><strong>transport_random</strong> <ul> <li><strong>r_vehicle_registration</strong> - generate random country specific vehicle registration plate.</li> <li><strong>r_icao</strong> - generate a random country specific aircraft registration code.</li> <li><strong>r_imo</strong> - generate a random vessel registration code.</li> </ul> </li> </ul> </p> <p>Also there are 3 new locale supported for names, addresses and more. These countries are Denmark, China and Dhubai. Performance improvements for Markov text generation are coming as well as new SWIFT and FIX financial random generation.</p> plsql promises - chaining and thenables 464C11564C15BB9DE050007F01003BC2 Sat, 21 Jan 2017 08:39:45 +0700 <p>So last blog entry <a href="">Do or do not.</a> on the promises library, covered the basics of what promises can give us.</p><p>This entry will cover more around chaining of promises and how you can easily run your code in parallel and still make sure they run in the right order, when needed.</p><p>Promises by definition has a method called <b>[then]</b>. What this method does, is that it will take the value of the promise once it is fulfilled, and use that as input to a new function defined by us. The input to then is, either a function to run when fulfilled or a function to run if rejected or both. Although not in the standard there are more and more libraries implementing a method called <b>[done]</b>. It has the same input options as the <b>[then]</b> method but it does not return a new promise. So only use this method when you do not care about the result of the chain call. Since we are in Oracle I cannot name the method <b>[then]</b> since it is a reserved word, so I had to add an _f to the name, so it becomes <b>[then_f]</b>.</p><p>So here is the first example. We create a promise based on the function p_multiplier, that takes a number and multiplies it by 2. We then say that if this promise is fulfilled we want to execute the function called p_multi_convert. This function takes the previous promise result, and will return a text that will tell us if the output is less or more than 50.</p><pre><code class="language-sql"> declare test_promise promise; begin test_promise := promise('p_multiplier', 42); test_promise := test_promise.then_f('p_multi_convert'); promises_ninja.promise_wait(test_promise); dbms_output.put_line('Value of test_promise2 is: ' || test_promise.getanyvalue); end; / </code></pre> Do, or do not. There is no "try". 456EF39023E4FEDCE050007F01006B83 Fri, 06 Jan 2017 10:44:20 +0700 <p>About 7 months ago, I was reading an article about some of the new features that were in javascript/ecma/coffeescript or whatever it is called now. One of the things that stuck out, was <a href="" location="_new">promises</a>. I liked the idea of "asynchronous" execution with a possible chained dependency, that you could just define and run, and then carry on with other tasks without having to wait for the result. What you do instead, is you receive a "promise" of the execution. A promise that at some point will contain the result from your call. </p><p>The Oracle database has the capability to do this already in dbms_scheduler using chains, but it is not dynamic and the complete flow has to be defined up front.</p><p>So I decided to try and see if this could be done in plsql somehow ... And then I got occupied with something else. Instead I picked up the idea over christmas, and decided to give it a go. What I have today is a 60% implementation, that should get to 100% over the next 2 weeks, but the stuff that is here now, is functional and you can do some fun pieces of code with it</p><p>Let me just give you a couple of samples of what <a href="">PROMISES_NINJA</a> is capable of:</p> Demographically correct test data 41160789E353E6F4E050007F01004D39 Sun, 13 Nov 2016 03:11:20 +0700 <p>One of the main reasons behind finishing versions <a href="">1.5.0 of RANDOM_NINJA</a>, was to be able to add the localization for different countries so that I could create test data sets, that are demographically correct.</p><p>So after adding that, the TESTDATA_NINJA package, can now create statistically correct data sets for 3 countries: <ul> <li>United States</li> <li>China</li> <li>Denmark</li> </ul></p><p>The following ratio of data will be correct according to UN Statistics and CIA World Book: <ul> <li><strong>Age group</strong> - Age ratios will be divided in 0-14, 15-64 and 65+</li> <li><strong>Female/Male</strong> - Gender rations will be divided within the different age groups, according to statistics</li> </ul> </p><p>Identification numbers and birthdays will also be in statistically correct ratios and in valid formats.</p> <p>As an example I created 3 test tables, by using the population generator from the testdata_ninja package:</p> <p><pre><code class="language-sql">create table t_us as select * from table(testdata_ninja.population('US', 0.00001)); create table t_dk as select * from table(testdata_ninja.population('DK', 0.00001)); create table t_cn as select * from table(testdata_ninja.population('CN', 0.00001)); </code></pre></p> Random fun 409B1D9F2082B622E050007F01005D7B Sun, 06 Nov 2016 07:07:11 +0700 <p>It has been some fun evenings lately. I have added a lot of new functionality and new data domains to the <a href="">RANDOM_NINJA</a> package. One of the bigger updates is that I have created a Markov Chain function for text generation, so the random text is a lot more real looking:</p> <p><pre><code class="language-sql">SQL> select text_data.markov_sentence from dual; MARKOV_SENTENCE -------------------------------------------------------------------------------------------------------------- In but thruout the entire world various kinds of traps and snares as. SQL> select text_data.markov_sentence from dual; MARKOV_SENTENCE -------------------------------------------------------------------------------------------------------------- Safe however that not one-half of the best trappers use them. It requires. SQL> select text_data.markov_sentence from dual; MARKOV_SENTENCE -------------------------------------------------------------------------------------------------------------- The trappers use them. It is a humane way of killing. SQL> </code></pre></p> <p>This really adds a lot of functionality in terms of testing text functionality and text indexing, as the generated text is much closer to how real text would look.</p> <p>The person_random has received a lot of job related functionality, so we can now generate job titles, salaries and more:</p> <p><pre><code class="language-sql">SQL> select person_random.r_jobsector from dual; R_JOBSECTOR -------------------------------------------------------------------------------------------------------------- Educational Services SQL> select person_random.r_jobtitle from dual; R_JOBTITLE -------------------------------------------------------------------------------------------------------------- Consultant SQL> select person_random.r_jobtitle(r_jobsector => 'Educational Services') from dual; PERSON_RANDOM.R_JOBTITLE(R_JOBSECTOR=>'EDUCATIONALSERVICES') -------------------------------------------------------------------------------------------------------------- Teacher SQL> select person_random.r_salary(r_jobsector => 'Educational Services') from dual; PERSON_RANDOM.R_SALARY(R_JOBSECTOR=>'EDUCATIONALSERVICES') ---------------------------------------------------------- 94260 SQL> r 1* select person_random.r_salary(r_jobsector => 'Educational Services') from dual PERSON_RANDOM.R_SALARY(R_JOBSECTOR=>'EDUCATIONALSERVICES') ---------------------------------------------------------- 50400 SQL> select person_random.r_jobsector from dual; R_JOBSECTOR -------------------------------------------------------------------------------------------------------------- Management SQL> </code></pre></p> <p>The finance_random package has been updated with features related to accounts and account data generation. So we can generate random IBAN and BBAN valid bank accounts for a lot of countries, and we can generate random transaction types and account balances:</p> <p><pre><code class="language-sql">SQL> select finance_random.r_accountnumber from dual; R_ACCOUNTNUMBER -------------------------------------------------------------------------------------------------------------- FO1361785488259274 SQL> select finance_random.r_accountnumber('DK') from dual; FINANCE_RANDOM.R_ACCOUNTNUMBER('DK') -------------------------------------------------------------------------------------------------------------- DK1848327576613652 SQL> select finance_random.r_accounttype from dual; R_ACCOUNTTYPE -------------------------------------------------------------------------------------------------------------- Investment Account SQL> r 1* select finance_random.r_accounttype from dual R_ACCOUNTTYPE -------------------------------------------------------------------------------------------------------------- Investment Account SQL> r 1* select finance_random.r_accounttype from dual R_ACCOUNTTYPE -------------------------------------------------------------------------------------------------------------- Savings Account SQL> select finance_random.r_accounttransaction('Savings Account') from dual; FINANCE_RANDOM.R_ACCOUNTTRANSACTION('SAVINGSACCOUNT') -------------------------------------------------------------------------------------------------------------- Deposit SQL> r 1* select finance_random.r_accounttransaction('Savings Account') from dual FINANCE_RANDOM.R_ACCOUNTTRANSACTION('SAVINGSACCOUNT') -------------------------------------------------------------------------------------------------------------- Deposit SQL> r 1* select finance_random.r_accounttransaction('Savings Account') from dual FINANCE_RANDOM.R_ACCOUNTTRANSACTION('SAVINGSACCOUNT') -------------------------------------------------------------------------------------------------------------- Withdrawal SQL> select finance_random.r_accounttransaction('Investment Account') from dual; FINANCE_RANDOM.R_ACCOUNTTRANSACTION('INVESTMENTACCOUNT') -------------------------------------------------------------------------------------------------------------- Dividend SQL> r 1* select finance_random.r_accounttransaction('Investment Account') from dual FINANCE_RANDOM.R_ACCOUNTTRANSACTION('INVESTMENTACCOUNT') -------------------------------------------------------------------------------------------------------------- Cap. Gains Short SQL> select finance_random.r_accountbalance from dual; R_ACCOUNTBALANCE ---------------- 287555.25 SQL> select finance_random.r_accountbalance('Savings Account') from dual; FINANCE_RANDOM.R_ACCOUNTBALANCE('SAVINGSACCOUNT') ------------------------------------------------- 430614.3 SQL> r 1* select finance_random.r_accountbalance('Savings Account') from dual FINANCE_RANDOM.R_ACCOUNTBALANCE('SAVINGSACCOUNT') ------------------------------------------------- 5411.24 SQL> </code></pre></p> Building Facebook or Germany .... 3FA734494D560E42E050007F01004259 Wed, 26 Oct 2016 09:08:36 +0700 <p>Whether it is for work, or we are just playing with a new idea back home, there comes a time when we need to create some test data for whatever it is we are testing. The biggest problem with creating test data, is creating some data, that actually looks like real data. Because we want "real" data, if we really want to test how our application works or performs. Things like index selectivity, histograms and much more inside oracle will all behave differently depending on what kind of data there are in your tables. So creating life like data, is important.</p><p>Luckily I have previously created a base library that generates random data within a lot of different data domains. The <a href="">RANDOM_NINJA</a> package can create all that data, but because of the required flexibility in that library, it might not be user friendly, if you just want to create some tables fast to test on. So I decided to create a library that is based on the random_ninja library but binds it together in a little more easy way to create data.</p><p>The library is based on generators. All generators are pipelined functions, making it easy to use in create table statements. All generators by default will return 10 rows, but that can be controlled by setting the testdata_ninja.g_default_generator_rows parameter.</p><p>In the future there will be more control options for the generators, apart from just the rowcount. The current available generators (and their fields) are:</p><p> <ul> <li><strong>people</strong> - Generate a table of people with basic information. <ul> <li><strong>Country</strong> - Country of the person.</li> <li><strong>Identification</strong> - The ID number of the person. Will be a valid ID based on the Country.</li> <li><strong>First name</strong> - First name. Will be country and gender specific if data is available in random_ninja.</li> <li><strong>Middle name</strong> - Possible middle name. Will be country and gender specific if data is available in random_ninja.</li> <li><strong>Last name</strong> - Last name. Will be country and gender specific if data is available in random_ninja.</li> <li><strong>Birthdate</strong> - Birthdate of the person.</li> <li><strong>Gender</strong></li> </ul> </li> <li><strong>users</strong> - Generate a table of website users. <ul> <li><strong>Username</strong> - Username of website user.</li> <li><strong>Email</strong> - User email address.</li> <li><strong>Address1</strong> - First part of address. Always present.</li> <li><strong>Address2</strong> - Second part of address. Randomly present.</li> <li><strong>Zipcode</strong> - Zipcode of the address.</li> <li><strong>State</strong> - State of the address.</li> <li><strong>Creditcard</strong> - Type of credit card.</li> <li><strong>Creditcard number</strong> - Creditcard number.</li> <li><strong>Creditcard expiry</strong> - Creditcard expiry.</li> <li><strong>Password</strong> - The hashed password.</li> </ul> </li> <li><strong>cdr</strong> - Generate a table of cdr records. <ul> <li><strong>Orig imsi</strong> - IMSI number of the originating caller phone.</li> <li><strong>Orig isdn</strong> - Phone number of originating caller.</li> <li><strong>Orig imei</strong> - IMEI of originating caller.</li> <li><strong>Call type</strong> - Call type.</li> <li><strong>Call type service</strong> - Call service type.</li> <li><strong>Call start latitude</strong> - Latitude of the originator at the start of the call.</li> <li><strong>Call start longtitude</strong> - Longtitude of the orginator at the start of the call.</li> <li><strong>Call date</strong> - Date of the call.</li> <li><strong>Call duration</strong> - Call length in seconds.</li> <li><strong>Dest imsi</strong> - IMSI number of the destination caller phone.</li> <li><strong>Dest isdn</strong> - Phone number of destination phone.</li> <li><strong>Dest imei</strong> - IMEI of destination.</li> <li><strong>Network operator</strong> - Network operator code.</li> </ul> </li> <li><strong>articles</strong> - Create a table of articles. <ul> <li><strong>Author</strong> - The author of the article.</li> <li><strong>Written</strong> - Date article is written.</li> <li><strong>Headline</strong> - Headline.</li> <li><strong>Lead paragraph</strong> - Leading paragraph.</li> <li><strong>Main article</strong> - The main part of the article.</li> <li><strong>End paragraph</strong> - Final articel paragrpah.</li> </ul> </li> </ul> </p> Lots of random data 3F6AF888A63D241CE050007F01007AF3 Mon, 24 Oct 2016 09:07:18 +0700 <p>After a couple of long weekends, I have finally reached what I think is a good first attempt of a random data generation package. The number of different domains that you can generate data for, should be enough to cover most general use cases.</p> <p>The package, or packages, are divided into a couple of subcategories to make it a bit more easy to get an overview of the different capabilities. You can see the below list of what you can do with this:</p> <p> <ul> <li><strong>core_random</strong> - The basic random functionalities required. <ul> <li><strong>r_bool</strong> - Random true/false values. Chance of true can be specified.</li> <li><strong>r_natural</strong> - Random natural numbers. Range can be specified.</li> <li><strong>r_character</strong> - Random character. Casing, Choice pool and Symbols can be specified.</li> <li><strong>r_float</strong> - Random float number. Range and precision can be specified.</li> <li><strong>r_integer</strong> - Random integer number. Range can be specified.</li> <li><strong>r_string</strong> - Random string. Length and character pool can be defined.</li> <li><strong>r_hex</strong> - Random hex string. Length can be defined.</li> </ul> </li> <li><strong>text_random</strong> - Generate random pieces of text, to simulate comments, descriptions, articles and more. <ul> <li><strong>r_syllable</strong> - Random syllables.</li> <li><strong>r_word</strong> - Random word. Number of syllables, length and capitalizon can be specified.</li> <li><strong>r_sentence</strong> - Random sentence. The number of words in the sentence can be specified.</li> <li><strong>r_paragraph</strong> - Random paragraph. Number of sentences can be specified.</li> </ul> </li> <li><strong>time_random</strong> - Generate random time and date components. <ul> <li><strong>r_second</strong> - Random second.</li> <li><strong>r_minute</strong> - Random minute.</li> <li><strong>r_hour</strong> - Random hour. am/pm format can be specified.</li> <li><strong>r_ampm</strong> - Random am or pm.</li> <li><strong>r_millisecond</strong> - Random millisecond.</li> <li><strong>r_year</strong> - Random year. Min and max can be specified, as well as two digits result if needed.</li> <li><strong>r_month</strong> - Random month. Season can be specified.</li> <li><strong>r_day</strong> - Random day. Month can be specified.</li> <li><strong>r_date</strong> - Random date. Any component of the date format can be fixed if defined.</li> <li><strong>r_epoch</strong> - Random epoch date.</li> <li><strong>r_timestamp</strong> - Random timestamp. Any component of the timestamp can be fixed if defined.</li> </ul> </li> <li><strong>location_random</strong> - A wide variety of random location related data. <ul> <li><strong>r_country</strong> - Random country. Either full name, or short ISO form can be specified.</li> <li><strong>r_height</strong> - Random height. Result in feet and livable height can be specified.</li> <li><strong>r_depth</strong> - Random depth. Result in feet, and depth on land and not ocean can be specified.</li> <li><strong>r_latitude</strong> - Random latitude angle. Precision can be specified.</li> <li><strong>r_longtitude</strong> - Random longtitude. Precision can be specified.</li> <li><strong>r_coordinate</strong> - Random coordinates as a pair of latitude and longtitude points.</li> <li><strong>r_altitude</strong> - Random altitude, from 0 to upper atmosphere. Result in feet can be specified.</li> <li><strong>r_state</strong> - Random state name. Shortform option available. Country can also be specified.</li> <li><strong>r_zipcode</strong> - Random zip code. Country can specified for country specfic formats.</li> <li><strong>r_street</strong> - Random street name. Country and shortform can be specified.</li> <li><strong>r_address</strong> - Random address. Country and max numbering of street location can be specified.</li> <li><strong>r_city</strong> - Random city name. Country and state can be specified.</li> <li><strong>r_address2</strong> - Random address 2 line, such as apartment or name of building. Country can be specified.</li> <li><strong>r_level</strong> - Random building level.</li> </ul> </li> <li><strong>person_random</strong> - Random personal related data. <ul> <li><strong>r_age</strong> - Random age. Type (child, teen, adult, senior) can be specified.</li> <li><strong>r_birthday</strong> - Random birthday date. As with age, type can be specified.</li> <li><strong>r_firstname</strong> - Random first name. Both country and gender can be specified.</li> <li><strong>r_middlename</strong> - Random middle name. Country and gender can be specified.</li> <li><strong>r_lastname</strong> - Random last name. Country and gender can be specified</li> <li><strong>r_name</strong> - Random name. Country, Gender, Include middlename, Middle initial and prefix can be specified.</li> <li><strong>r_gender</strong> - Random gender.</li> <li><strong>r_prefix</strong> - Random prefix. Gender and country can be specified.</li> <li><strong>r_identification</strong> - Random valid identification number, based on the country specified.</li> <li><strong>r_suffix</strong> - Random suffix. Country and shortform can be specified.</li> </ul> </li> <li><strong>phone_random</strong> - Generate random data related to phones. <ul> <li><strong>r_imei</strong> - Random <u><i>valid</i></u> IMEI number. IMEISV version can be specified.</li> <li><strong>r_meid</strong> - Random <u><i>valid</i></u> MEID number.</li> <li><strong>r_country_calling_code</strong> - Random <u><i>valid</i></u> international code. + or 00 can be specified.</li> <li><strong>r_phonenumber</strong> - Random <u><i>valid</i></u> phone number. Generates <u><i>valid</i></u> landline or mobile numbers. Country and country code can be specified.</li> <li><strong>r_mcc</strong> - Random <u><i>valid</i></u> MCC code. Country can be specified.</li> <li><strong>r_mnc</strong> - Random <u><i>valid</i></u> MNC code. Country can be specified.</li> <li><strong>r_imsi</strong> - Random <u><i>valid</i></u> IMSI number. Country can be specified.</li> <li><strong>r_call_type</strong> - Random call type, for CDR data.</li> <li><strong>r_call_type_service</strong> - Random call type service, for CDR data.</li> <li><strong>r_operator_code</strong> - Random and <u><i>valid</i></u> operator code (pmnl) for CDR records. Country can be specified.</li> </ul> </li> <li><strong>finance_random</strong> - Generate random financial data. <ul> <li><strong>r_currency</strong> - Random <u><i>valid</i></u> ISO currency. ISO shortform can be specified.</li> <li><strong>r_currencypair</strong> - Random base and quote currencies. Both can be specified.</li> <li><strong>r_creditcard</strong> - Random <u><i>valid</i></u> credit card name. Shortform can be specified.</li> <li><strong>r_creditcardnum</strong> - Random <u><i>valid</i></u> creditcard number. Creditcard type can be specified.</li> <li><strong>r_expirydate</strong> - Random credit card expiry date. Future data can be specified.</li> <li><strong>r_amount</strong> - Random amount. Range and precision can be specified.</li> </ul> </li> <li><strong>web_random</strong> - Generate random web/internet related data. <ul> <li><strong>r_tld</strong> - Random top level domain. Generic and country inclusion can be specified.</li> <li><strong>r_domain</strong> - Random domain name. TLD can be specified.</li> <li><strong>r_email</strong> - Random email address. Specify if you want to use real name.</li> <li><strong>r_ipv4</strong> - Random <u><i>valid</i></u> ipv4 ip address.</li> <li><strong>r_url</strong> - Random URL. Specify if you want to use https and if you want to add query parameter.</li> <li><strong>r_ipv6</strong> - Random <u><i>valid</i></u> ipv6 ip address.</li> </ul> </li> <li><strong>consumer_random</strong> - Generate random consumer related data. <ul> <li><strong>r_category</strong> - Random consumer category. You can choose between all, food ro non-food categories.</li> <li><strong>r_food_item</strong> - Random food item. Category can be specified.</li> <li><strong>r_nonfood_item</strong> - Random non-food item. Category can be specified.</li> <li><strong>r_service_item</strong> - Random service related item. Category can be specified.</li> </ul> </li> </ul> </p> <p>Phew... no wonder I felt like this was taking a lot of time to create. I really hope that people can use this for something. I know that there are several times where I have to create random test data, and I always end up using excel, or even worse, just one row with 123,123,123,asdf,asdf like data.</p><p>Now we have a better option</p> Generating random data 3DCC872FC83EDD55E050007F01001568 Sat, 01 Oct 2016 23:40:36 +0700 <p>We all need to create random data every now and again. Most of the times I have resolved to simply using <a href="">dbms_random</a> to generate random strings and numbers. The problem with approach though, is that data does not look like "real" data, and indexing will not be realistic. The Alexandria library contains a package that has a few functions <a href="">random_util_pkg</a>, but it is limited in the type of data you can create, and I felt that there were a couple of more parameters where I needed a bit more control on the output.</p> <p>So I have created <a href="">RANDOM_NINJA</a> which for now has the basic functions that I needed.</p><p>Just see the quick demo I have created below:</p> NPG - The package manager for Oracle PL/SQL 3B756949B69ADE86E050007F01007BA1 Thu, 01 Sep 2016 12:23:11 +0700 I finally got the most rough edges done now. After a long time of trying to find some spare time during the evenings, I have completed what I think, has been a great feature missing from PL/SQL for a long long time: A real package manager. I've always believed that PL/SQL has a great community and that there exists a lot of packages out there, that deserves a broader audience. Not only that, but it needs to be easier to share and install these community packages.<p>Say welcome to NPG, an oracle package manager for PL/SQL. It supports most of the basic features that package managers from other languages does (NPM, RubyGems, PIP etc) and I will add more and more functionality to it, over the coming weeks.</p>