Home › projects › Prolint Issue Tracker

Issues for Prolint Issue Tracker

SummaryStatusPriorityCategoryLast updatedAssigned tosort icon
temp-table defined without unique indexactivenormalfeature request12 years 42 weeks
rule tablename false positives when forward functiactivenormalbug report10 years 19 weeks
functions (and ips) should not use variables in maactivenormalfeature request12 years 46 weeks
input blocking statement during database transactiactivenormalfeature request12 years 46 weeks
MESSAGE statement not closed with a periodactivenormalfeature request12 years 42 weeks
Prolint Result messages?activenormalsupport request10 years 42 weeks
Prolint - tablename rule for class method parameteactivecriticalbug report3 years 11 weeks
insufficient index information specified in WHERE-activenormalfeature request12 years 46 weeks
buffer in a FOR EACH statement is affected by IPactivenormalfeature request12 years 42 weeks
BUFFER name must not match table nameactivenormalfeature request11 years 37 weeks
function or non-void method should return a valueactivenormalfeature request8 years 16 weeks
no DEFINE statements between executable statementsactivenormalfeature request12 years 46 weeks
check if every RECORD_NAME and Field_Ref are qualiactivenormalfeature request12 years 42 weeks
idea: configure Prolint rules by application layeractivenormalfeature request12 years 33 weeks
NOUNDO: false positive on dataset-handlesactivenormalbug report9 years 25 weeks
check if each opened stream is closedactivenormalfeature request12 years 46 weeks
transaction-distinct: don't start a remote transacactivenormalfeature request12 years 42 weeks
probably bad roundingactivenormalfeature request12 years 42 weeks
widget X created but never deletedactivenormalfeature request12 years 46 weeks
transaction scoped to comp.unit level?activenormalfeature request12 years 42 weeks
1234next ›last »
#
Syndicate content