This post has come about – again – due to being in the middle of  creating a brand new Website using CodeIgniter ( A PHP Framework) , MySQL and Stored Procedures.

Don’t worry about what they are, but what happened is I went out on a limb and started delving into Stored Procedures that return multiple DataSets. Something I’ve not had to deal with up till now. And a long story Short – CodeIgniter was a bit short on letting me do that. I like CodeIgniter and once you get your head around it, it does let you create your wonderful masterpiece of a Script without having to worry about all the housekeeping code.

Anyway, retrieving the multiple Datasets just wasn’t happening. A shortfall of CodeIgniter.

So I had a problem on my hands.

What did I do to solve it?

Simple, I opened up my trusty Open Office Writer – created a new document called – “Using MySQL Stored Procedures -A .odt” and started writing out the problem.

It’s very  important to actually State the problem. Then you can start writing out what isn’t happening. What you think should happen and you’ll eventually get somewhere. The reason being you are writing down what you need to do and you’ll be writing down what you have done… That’s where this works wonderfully well.

Yes, it takes a little bit longer to do than just blast away. But guess what! Taking your time actually helps. Plus you’ll more than likely create yourself a guide on the problem and how you solved it.

Any light bulbs going off yet? If you know of others who might be having the same problem….you’ve just written an Ebook about it, or the makings of one.

Actually with my particular problem, I noted that it would be beneficial to go back to basics and I documented everything… The PHP Code I created. That Database Tables, The Stored procedures. I even came up with a way to automatically install my Database from a Script loaded with all my SQL statements. That got included so I don’t forget….

So I got the main script working and tinkered till I got it right and wrote it all down.

Guess What?

I ended up discovering all the right ways to do what I wanted then I got into the guts of the CodeIgniter Framework and after a bit of headscratching I got it all working.

So now I have sample Scripts, The Ebook on what I did, and a working CodeIgniter Framework that has come up pretty swish ( which means Fantastic ). Now I can get back onto my project and keep going…

The whole point of this is to remember. When you have a problem. Write it out!!!!

I’ve still got a little tidying up of the Ebook before I unleash it upon the world. But for now – it’s a good guide for me for tomorrow. Hmm yes, that’s about how long my whatever that kind of memory is called… I forget..But at least I know where to find the info I’ve written down.

Find or create the problem, Solve it Once, Write it down Once and if it pops up again – you just re-read what you did last time. Absolutely Brilliant!

It does take some commitment to do this. But ask yourself, how important is it to you – to solve the problem you have.

If you do have any Techy Website or other kind of problems. Give me a shout. I’ll work it out – write it out and send you the result. I’ve done it before for others and I’ll do it again.

Are you thinking….”This is a great way to create Content”? You should be!

Ok well I had best get into documenting up the CI changes in another document…. That’s a bit too much for any poor soul to have to read through in the one book and it’s another problem.

Happy Problem Solving.

“If you aint having any problems with anything, you aint doing anything new OR you forgot how you solved it last time”

Till next time

Cheers

Tim Brownlaw… Now where did  I put those files………

On the "off chance" that you actually liked this post,
how about liking us on Facebook?...

Powered By Facebook Like Post Plugin