Home › projects › Prolint Issue Tracker

Issues for Prolint Issue Tracker

SummaryStatusPrioritysort iconCategoryLast updatedAssigned to
enforce the order of keywordsactivenormalfeature request12 years 46 weeks
BUFFER name must not match table nameactivenormalfeature request11 years 37 weeks
abbreviation of database field names is not alloweactivenormalfeature request12 years 46 weeks
locate private methods that are never calledactivenormalfeature request11 years 3 weeks
insufficient index information specified in WHERE-activenormalfeature request12 years 46 weeks
database access not allowed in certain classesactivenormalfeature request11 years 3 weeks
type mismatch in parameter X when calling user-defactivenormalfeature request12 years 46 weeks
request rule: SUPER should be last call in a 'tearactivenormalfeature request11 years 2 weeks
memory in memptr X is never released with set-sizeactivenormalfeature request12 years 46 weeks
Prolint Result messages?activenormalsupport request10 years 42 weeks
widget X created but never deletedactivenormalfeature request12 years 46 weeks
input blocking statement during database transactiactivenormalfeature request12 years 46 weeks
core/Prolint.p gives error on get-row()fixednormalbug report10 years 22 weeks
"IF AVAILABLE" missing after "FIND NO-ERROR"activenormalfeature request12 years 42 weeks
namecheckfixednormalbug report10 years 21 weeksjurjen
EXCLUSIVE-LOCK downgraded to SHARE-LOCK after tranactivenormalfeature request12 years 42 weeks
rule tablename false positives when forward functiactivenormalbug report10 years 19 weeks
transaction-distinct: don't start a remote transacactivenormalfeature request12 years 42 weeks
Check if propsuper is runningactivenormalbug report10 years 13 weeks
Don't cast recid to integer or vice versaactivenormalfeature request12 years 42 weeks
« first‹ previous1234next ›last »
#
Syndicate content