Home › projects › Prolint Issue Tracker

Issues for Prolint Issue Tracker

SummaryStatusPriorityCategorysort iconLast updatedAssigned to
EXCLUSIVE-LOCK downgraded to SHARE-LOCK after tranactivenormalfeature request12 years 42 weeks
transaction-distinct: don't start a remote transacactivenormalfeature request12 years 42 weeks
Don't cast recid to integer or vice versaactivenormalfeature request12 years 42 weeks
Roundtable schema-update proceduresactivenormalfeature request12 years 42 weeks
UDF in WHERE-clauseactivenormalfeature request12 years 42 weeks
check if every RECORD_NAME and Field_Ref are qualiactivenormalfeature request12 years 42 weeks
find "dead code"activenormalfeature request12 years 42 weeks
new rule: cleanup-code can be moved into a finallyactivenormalfeature request8 years 19 weeks
clean up inactivated codeactivenormalfeature request12 years 42 weeks
function or non-void method should return a valueactivenormalfeature request8 years 16 weeks
an IP should not access variables/buffers that areactivenormalfeature request12 years 42 weeks
Detect unused USINGactivenormalfeature request7 years 21 weeks
buffer in a FOR EACH statement is affected by IPactivenormalfeature request12 years 42 weeks
use EMPTY TEMP-TABLEactivenormalfeature request12 years 42 weeks
Find absolute path names in the codeactivenormalfeature request12 years 42 weeks
transaction scoped to comp.unit level?activenormalfeature request12 years 42 weeks
MESSAGE statement not closed with a periodactivenormalfeature request12 years 42 weeks
adecomm.pl not available in OEArchitectactivenormalsupport request8 years 19 weeksjurjen
Prolint Result messages?activenormalsupport request10 years 42 weeks
Use of dbaliases.d - prolint 74activenormalsupport request7 years 14 weeks
« first‹ previous1234next ›last »
#
Syndicate content