IMO this should be kept at least till the next major release, the problem is that it involves changing all the the logic and work arounds that we did,trying to avoid the hassle of extending the turbineUser, so if we want to migrate a project that already utilizes this logic, it will be quite a mess I guess. so keep it for backword compatibility and mention in your release docs that you disencourage users from using this approach because so and so and that it be deprecated in the next major release. regards Akmal ----- Original Message ----- From: "Quinton McCombs" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, March 21, 2003 5:19 AM Subject: [POLL] Deprecation of the OBJECT_DATA column in TURBINE_USER table
> The use of perm scope pull tools and storing data in the TurbineUser > using the setPerm() method would be affected by this change. > > Both of these cause data to be serialized into the OBJECT_DATA column in > the TURBINE_USER database table. Since Torque (actually Village) has > issues using the BLOB datatype, there is an upper limit to the amount of > data that can be stored in this manner. Everything will work fine until > you hit this limit then you will start getting database errors. > > The downsides to using setPerm() in TurbineUser are discussed in the > extending turbine user how to. To summarize, this data can not be used > to select from the database and is very difficult to extact using a > third party tool that accessed the database directly. > > It is a very simple process to start storing this data in database > columns using the DBSecurityService. It is even easier if you use the > new TorqueSecurityService that Henning wrote which is availiable in 2.3. > > If you truly have a need for perm scope tools, you can get the same > functionality using the new authorized scope tool in 2.3. Just like the > perm scope tool, the authorized tool is initialized with an instance of > the user object. During the initialization of the tool, you can get any > data that you need to maintain state across logins from the user object. > Just add any data that you previously stored in the perm tool to the > user object using database columns to store your data. > > I am proposing that the use of the OBJECT_DATA column be deprecated in > 2.3. Is there anyone that this will cause a problem for? > > -------------------------------------------- > Quinton McCombs > NequalsOne - HealthCare marketing tools > mailto:[EMAIL PROTECTED] > http://www.NequalsOne.com > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
