On 11/03/2013 05:01 PM, Mark Rotteveel wrote: > On 31-10-2013 17:31, Alex Peshkoff wrote: >> On 10/31/13 20:20, liviusliv...@poczta.onet.pl wrote: >>> Hi, >>> >>> We store in thouse fields data usefull for application logic. Some dep info >>> or sime restriction. This was choose of project design at start and >>> changing it now will be risk but possible. Problem is that some projects >>> are also not created by us and discontinued and wthout source code. We only >>> add e.g extension plugin and this life from years. >>> >> UID and GID (although shown by gsec) are not supported currently by SRP >> plugin. They were never used in firebird itself, just artifact. >> Certainly it's not too hard to add them to SRP, but I'm not sure that >> supporting useless for most of people fields is a good idea. The best >> solution for you is to have personal version of SRP management plugin. >> Certainly, if not only you use this fields in app logic, looks like we >> will have to add them and support till the end of FB days. > I'd like to argue that some things shouldn't be supported forever on the > off chance that people are abusing it in some way. This specific example > might indicate a need to persist information with a user. What about > adding some sort of extensible property support which can add properties > (name-value pairs) to users (which are stored in the security database > and can be managed using the services API in some way).
Thats' great suggestion. ------------------------------------------------------------------------------ Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
