List Info

Thread: {Spam?} Re: Comments on a Database




{Spam?} Re: Comments on a Database
user name
2007-05-15 19:10:30
Also,

If you are using postgres (I don't know mysql all that well)
you can
use rules or triggers to limit the claim_reject to 4
fields.

On 5/15/07, Rob Wilkens <robwilkensgmail.com> wrote:
> Just a quick observation that is probably completely
useless to you:
>
> I noticed one of your tables ("claims") had
:
> claim_reject_1
> claim_reject_2
> claim_reject_3
> claim_reject_4
>
> I'm no database master, but from what limited sql
knowledge I've
> learned from others, I've been given the impression
that sequential
> fields like that are bad.  You're better off, I think,
having a
> claim_reject table with maybe the claim id, and the
reject number,
> then reject description (or date or whatever) fields in
it.  This
> would allow for an arbitrary number of claim_rejects to
be entered.
> Admittedly, you may "only need 4 now" but you
want something generic,
> so maybe having it the way I'm suggesting might come
closer to the
> generic goal.
>
> I haven't had time otherwise to look through all that,
and no, I don't
> necessarily know what I'm talking about.
>
> -Rob
>
> On 5/15/07, Chuck Reeves <creevesdja.com> wrote:
> > So I need to build a front-end for:
> >
> > MailScanner has detected a possible fraud attempt
from "206.34.186.161"
> > claiming to be MailScanner warning: numerical
links are often malicious:
> > http://206
.34.186.161/sqlReports/pcim.html
> >
> > The goal here is make a generic as possible
front-end for processing
> > rebates.   This basically needs to be able the
take in a claim and (only if
> > the claim qualifies) print a check for it.  Im in
the beginning stages for
> > this and would gladly take any christizim on the
database structure, also
> > some advice on how to get this nightmare
programmed.
> > --
> Thank You,
> Chuck Reeves
> Developer
> Don Jagoda Associates
> 100 Marcus
> > Dr
> Melville, NY 11747
> Phone: 631-454-1800 Ex 344
> Fax: 631-454-1835
> >
> > _______________________________________________
> > Liphp mailing list
> > Liphpbuoy.com
> > ht
tp://www.buoy.com/cgi-bin/mailman/listinfo/liphp
> >
> >
>
>
> --
> Rob Wilkens
> http://RobWilkens.com
> 516-874-0579
>
> _______________________________________________
> Liphp mailing list
> Liphpbuoy.com
> ht
tp://www.buoy.com/cgi-bin/mailman/listinfo/liphp
>

_______________________________________________
Liphp mailing list
Liphpbuoy.com
ht
tp://www.buoy.com/cgi-bin/mailman/listinfo/liphp

Re: {Spam?} Re: Comments on a Database
country flaguser name
United States
2007-05-16 08:57:56
We are actually using MYSQL 5.0 for this database.&nbsp; I can see your point in not limiting it to 4 reject codes thats just been the standard and we never have needed more.  If I were to use a trigger, how would I go about using that ?  My thought would be having one field for reject (VARCHAR(250)) that concats all the reject codes?

Justin Dearing wrote:
mail.gmail.com" type="cite">
Also,

If you are using postgres (I don't know mysql all that well) you can
use rules or triggers to limit the claim_reject to 4 fields.


On 5/15/07, Rob Wilkens gmail.com"><robwilkensgmail.com&gt; wrote:
  
Just a quick observation that is probably completely useless to you:

I noticed one of your tables ("claims") had :
claim_reject_1
claim_reject_2
claim_reject_3
claim_reject_4

I'm no database master, but from what limited sql knowledge I've
learned from others, I've been given the impression that sequential
fields like that are bad.  You're better off, I think, having a
claim_reject table with maybe the claim id, and the reject number,
then reject description (or date or whatever) fields in it.  This
would allow for an arbitrary number of claim_rejects to be entered.
Admittedly, you may "only need 4 now" but you want something generic,
so maybe having it the way I'm suggesting might come closer to the
generic goal.

I haven't had time otherwise to look through all that, and no, I don't
necessarily know what I'm talking about.

-Rob

On 5/15/07, Chuck Reeves dja.com">&lt;creevesdja.com>; wrote:
    
So I need to build a front-end for:

MailScanner has detected a possible fraud attempt from "206.34.186.161"
claiming to be MailScanner warning: numerical links are often malicious:
MailScanner has detected a possible fraud attempt from "206.34.186.161" claiming to be MailScanner warning: numerical links are often malicious: http://206.34.186.161/sqlReports/pcim.html

The goal here is make a generic as possible front-end for processing
rebates.   This basically needs to be able the take in a claim and (only if
the claim qualifies) print a check for it.  Im in the beginning stages for
this and would gladly take any christizim on the database structure, also
some advice on how to get this nightmare programmed.
--
      
Thank You,
Chuck Reeves
Developer
Don Jagoda Associates
100 Marcus
    
Dr
      
Melville, NY 11747
Phone: 631-454-1800 Ex 344
Fax: 631-454-1835
    
_______________________________________________
Liphp mailing list
buoy.com">Liphpbuoy.com

http://www.buoy.com/cgi-bin/mailman/listinfo/liphp



      
--
Rob Wilkens
http://RobWilkens.com
516-874-0579

_______________________________________________
Liphp mailing list
buoy.com">Liphpbuoy.com

http://www.buoy.com/cgi-bin/mailman/listinfo/liphp


    

_______________________________________________
Liphp mailing list
buoy.com">Liphpbuoy.com

http://www.buoy.com/cgi-bin/mailman/listinfo/liphp


  

-- 
Thank You,
Chuck Reeves
Developer 
Don Jagoda Associates
100 Marcus Dr
Melville, NY 11747
Phone:  631-454-1800 Ex 344
Fax: 631-454-1835
[1-2]

about | contact  Other archives ( Real Estate discussion Medical topics )