I will then propose the following solution: Adding an argument to the user saving routine, and checking whether the user already exists if that is not set, and exposing that to the user interface, with a default to check and raise an exception if it is not set.
That seems like the cleanest solution here. Best Wishes, Chris Travers ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Ledger-smb-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel
