****************Could you be so kind as to have a read of me :3?****************
EDIT (12/09/2012): Since I've had so many people asking, YES, THE CAT AT 4:44 IS DIMSTAR/LIGHT FROM DIMSTAR'S PAST!! Urnam7 requested him to be a cameo (which I was going to do anyway, so awesome :'D) in a journal on Deviantart, so yes, story told.
Thank god this thing's out the way x.x It's such a boring episode :C ALL THEY DO IS TALK AAAHHHHH.
Anywho, so, after yet more time, episode 3 has hit your computer screens :) But let me give you a liiiitttle list of reasons why it's probably gonna take this long again...
1. Next episode has loads of... walking and irritating stuff like eating to animate.
2. I'm in my final school year, studying Biology, Chemistry and Physics, and I HAVE to work all out to get 3 As so I can successfully apply to University to study vet medicine (the first exams are January, so gonna die on here for a while, and the last lot are the end of May).
3. There is an entrance test for 2 Vet schools that I need to study for to give me the maximum chance of a place.
4. I'm trying to get into the GB squad for Archery.... which means many an hour shooting at the same ol' target face.
5. Unknown Blood first b*tch ;)
But here is a list why it will still happen:
1. I have to have a knee operation and will not be able to do any more work experience or gym sessions, so more free time.
2. I am determined to keep this series going, and I can take both my laptop and Desktop to Uni with me, which has all my animation tools on it :)
MUCHOS thank you to Zach6700 for steping in as Greystripe's 3rd voice (oops) and being awesome and quick with lines etc. . Actually, thank you ALL epic voice actors :D (a lot of which were hired JUST for this ep :O)
I DO NOT OWN ANY OF THE MUSIC OR CLAIM TO OWN IT, OR THE WARRIOR CATS SERIES!!!! I do however own all drawn work, SOME of the backgrounds and SOME character designs.
If you've come here from dA, have a look for your character if you submitted one, I did use them all :D
Thank you so much for being so paitient, and thank you so much for nearly 4,000 subscribers :'D (how how HOW?!!??!!?)
(c)Lightning Strike Productions
I'm on the second series of Warrior Cats. it is kind of sad to realize how fast paced it all is, in your head at least. We see Rusty to Firepaw to Fireheart then Firestar. Then his own kits. As well as his own nephew and his kits.
God this gave me the feels so hard
I think that "Fire" is Fireheart and "Ice" is Greystripe. They're opposites and they fight in the book, but I haven't read the book in 2 years. If it's not that Fire and Grey argue a lot then it's winter that is the "Ice"
A trigger is a named PL/SQL unit that is stored in the database and executed ( fired ) in response to a specified event that occurs in the database.
Overview of Triggers.
A trigger is a named program unit that is stored in the database and fired (executed) in response to a specified event. The specified event is associated with either a table, a view, a schema, or the database, and it is one of the following:
A database manipulation (DML) statement ( DELETE , INSERT , or UPDATE )
A database definition (DDL) statement ( CREATE , ALTER , or DROP )
A database operation ( SERVERERROR , LOGON , LOGOFF , STARTUP , or SHUTDOWN )
The trigger is said to be defined on the table, view, schema, or database.
A DML trigger is fired by a DML statement, a DDL trigger is fired by a DDL statement, a DELETE trigger is fired by a DELETE statement, and so on.
An INSTEAD OF trigger is a DML trigger that is defined on a view (not a table). The database fires the INSTEAD OF trigger instead of executing the triggering DML statement. For more information, see Modifying Complex Views (INSTEAD OF Triggers).
A system trigger is defined on a schema or the database. A trigger defined on a schema fires for each event associated with the owner of the schema (the current user). A trigger defined on a database fires for each event associated with all users.
A simple trigger can fire at exactly one of the following timing points :
Before the triggering statement executes.
After the triggering statement executes.
Before each row that the triggering statement affects.
After each row that the triggering statement affects.
A compound trigger can fire at more than one timing point. Compound triggers make it easier to program an approach where you want the actions you implement for the various timing points to share common data. For more information, see Compound Triggers.