Hi!

Good. But it would be much better if priority will depend on the number of developers that want to see feature implemented. And not only developers that attend DEVCONs and write articles, but also thous that are too little to reach this ERs database. I hope you know what I meant.

>Someone just sent me a collection of ERs that I thought were organized quite well in that they offer scenarios, workarounds and other factors we often take into consideration when choosing which ones to implement. Here is an example of one:
>
>Topic: Referential Integrity enforced by the database engine
>
>Category: ER
>
>Priority: 2
>
>Current state: RI is enforced through complex VFP program stored in DBC
>
>Required functionality: Referential Integrity enforced by the database engine
>
>Scenarios: Current implementation is too complex. For bigger DBC this triggers can be largest than limit for stored procedures. Code is undocumented.
>
>Workaround: Write specific program that is smaller, more effective and documented, such as the one described in Effective Techniques by Jim Booth and Steve Sawyer.
>
>Contact: kosina@vol.cz