Home › projects › Prolint Issue Tracker

Issues for Prolint Issue Tracker

SummaryStatusPriorityCategoryLast updatedsort iconAssigned to
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
clean up inactivated codeactivenormalfeature request12 years 42 weeks
an IP should not access variables/buffers that areactivenormalfeature request12 years 42 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
Dataserver portabilityactivenormalfeature request12 years 42 weeks
no literal numbersactivenormalfeature request12 years 42 weeks
probably bad roundingactivenormalfeature request12 years 42 weeks
temp-table defined without unique indexactivenormalfeature request12 years 42 weeks
ambiguous findactivenormalfeature request12 years 42 weeks
memory leaksactivenormalfeature request12 years 42 weeks
idea: configure Prolint rules by application layeractivenormalfeature request12 years 33 weeks
"put-key-value" without "no-error"activenormalfeature request12 years 5 days
Give a warning when CURRENT-VALUE(SomeSequence) / activeminorfeature request11 years 46 weeks
« first‹ previous1234next ›last »
#
Syndicate content