RE: pL/SQL PROCEDUR

2002-03-27 Thread Paul Vincent
The proximity of the words BLOB and porn is unpleasantly evocative... -Original Message- Sent: 26 March 2002 19:25 To: Multiple recipients of list ORACLE-L ok it's done. check your database. I also populated it with all the URL links to child-porn. the FBI is knocking at your door

Re: pL/SQL PROCEDUR

2002-03-26 Thread DBarbour
Roland, What a surprise! I thought you were moving to an Access list? Because I've taken a rather perverse interest in the questions you ask, I'll give you a hint: triggers and exception handling. By the way, if no one has answered your question regarding a table of table definitions, it's

RE: pL/SQL PROCEDUR

2002-03-26 Thread Mark Leith
LMAO Obligatory Oracle Question: Does anybody have a sample init.ora file that they use for a 9.0.1 instance, for a sandbox database on Win2K with 512Mb RAM? Basically for my desktop PC play database.. -Original Message- [EMAIL PROTECTED] Sent: 26 March 2002 16:39 To: Multiple

RE: pL/SQL PROCEDUR

2002-03-26 Thread Grabowy, Chris
Can someone please create a table for me? Umm...I need last and first name columns. I don't want the DDL, I want you to connect to my database and create it for me. I need this done yesterday. Thanks, really, thanks. Hurry up!! -Original Message- Sent: Tuesday, March 26, 2002 11:59

Re: pL/SQL PROCEDUR

2002-03-26 Thread Jan Pruner
And do you expect a link or a real example script??? On Tue 26. March 2002 19:29, you wrote: Can someone please create a table for me? Umm...I need last and first name columns. I don't want the DDL, I want you to connect to my database and create it for me. I need this done yesterday.

RE: pL/SQL PROCEDUR

2002-03-26 Thread Mercadante, Thomas F
ok it's done. check your database. I also populated it with all the URL links to child-porn. the FBI is knocking at your door right now. check the BLOB columns. pretty nasty stuff stored there. -Original Message- Sent: Tuesday, March 26, 2002 1:29 PM To: Multiple recipients of list

RE: pL/SQL PROCEDUR

2002-03-26 Thread Grabowy, Chris
Even though I am beyond lazy, I don't write any code, or RTFM (remind us of someone??)...I did manage to steal some auditing triggers from Rachel C. and place them on the new table. When Tom inserted those nasty pictures, the trigger fired and emailed Tom's name, address, phone number, height,

RE: pL/SQL PROCEDUR

2002-03-26 Thread Mercadante, Thomas F
you forgot DNA sample. Rachel's good, but come-on! not THAT good. -Original Message- Sent: Tuesday, March 26, 2002 2:54 PM To: Multiple recipients of list ORACLE-L Even though I am beyond lazy, I don't write any code, or RTFM (remind us of someone??)...I did manage to steal some

Re: pL/SQL PROCEDUR

2002-03-26 Thread bill thater
[EMAIL PROTECTED] wrote: you forgot DNA sample. Rachel's good, but come-on! not THAT good. wanna bet?;-) PS for those of you who remember and were following my job saga, we were sold yesterday. well, partly sold anyway. the closing is 4/10 and we're still not sure if there will be any

Re: PL/SQL - procedur

2002-03-25 Thread Jan Pruner
Look at Exception in PL/SQL and how to use it. http://otn.oracle.com/docs/products/oracle8i/doc_library/817_doc/appdev.817/a77069/11_elems.htm#8355 And don't use 'date' type of variable to store start time and end time of your procedures. JP On Mon 25. March 2002 12:23, you wrote: Hallo,

RE: PL/SQL - procedur

2002-03-25 Thread Jesse, Rich
Jan, Could you explain why you say not to use the DATE datatype? Rich Jesse System/Database Administrator [EMAIL PROTECTED] Quad/Tech International, Sussex, WI USA -Original Message- Sent: Monday, March 25, 2002 6:33 AM To: Multiple recipients of

RE: RE: PL/SQL - procedur

2002-03-25 Thread Stephane Faroult
Could you explain why you say not to use the DATE datatype? Rich Jesse System/Database Administrator [EMAIL PROTECTED] Quad/Tech International, Sussex, WI USA Because of the 1s precision limit. The obvious workaround is to have PL/SQL procedures which

Re: PL/SQL - procedur

2002-03-25 Thread Jan Pruner
Because it stores only seconds and if your procedure's runtime is short ( 1 sec) you will get the same numbers. Other problem is: if you call same procedure in LOOP, you will get 1 - 2 - 5 ... 15 ... 500 records with same value in start and end time column. And (I think so) there's no way