Well, what I see more commonly is that a developer does work with MySQL and then deploys to another architecture for QA and Prod.
Ultimately, there won't be more than a hundred serialized Example class objects in my table at a time. Users will create them for a specific need within a given time frame, and after that time frame has passed, they can be safely removed. Therefore, I won't have to worry much about changing architectures, and if the architecture does change, I won't need to re-architect the serialized Example class, just make sure the dynamic SQL is generated properly (assuming datatypes are consistent). The only issue I COULD have, is if the data structure of the table changes, in which case, the Example class won't match any longer, and unserializing the stored objects would throw an exception. I suppose I could use "domainObjectName" on the table to define a class name with a version number, and then inspect the serialized XML to determine which class to use to unserialize it into, but still, the table schema won't match. -Ryan On Mon, Feb 25, 2008 at 1:16 PM, Kezerashvili, Denis < [EMAIL PROTECTED]> wrote: > I've been involved in two migrations in two different companies. One from > Oracle to Sybase, another one from Sybase to DB2. DB switch does happen in > real life in real companies. > > ------------------------------ > *From:* Jason Kratz [mailto:[EMAIL PROTECTED] > *Sent:* Monday, February 25, 2008 3:29 PM > *To:* [email protected] > *Subject:* RE: Save Generated WHERE Clause > > Of course you'd also have to ask how likely is a DB vendor switch? I > hear that argument a lot (don't use feature X….you might want to switch > databases some day!) and have yet to hear of many cases where a DB vendor > switch actually happened. > > > > Jason > > > > *From:* Ryan Shelley [mailto:[EMAIL PROTECTED] > *Sent:* Monday, February 25, 2008 2:26 PM > *To:* [email protected] > *Subject:* Re: Save Generated WHERE Clause > > > > Well, if I serialize the Example class, then changing the db vendor isn't > an issue, but it's a very good point if I decided to save the actual built > SQL statement. > > -Ryan > > On Mon, Feb 25, 2008 at 11:13 AM, Nathan Maves <[EMAIL PROTECTED]> > wrote: > > not to rain on the parade but I think the idea of storing sql would be a > bad thing. Just imagine the amount of work in the event of a DB vendor > switch.... ouch > > I would say think outside the box and find a different solution to storing > the save criteria. Even the idea of serializing the Java class gives me > chills. > > > > On Mon, Feb 25, 2008 at 11:27 AM, Ryan Shelley <[EMAIL PROTECTED]> > wrote: > > You're correct about the Abator example class. The idea is that there > will be records in the database that my users want to extract based upon > their own criteria. I can allow them to filter dynamically based upon the > Example classes, however, if they want to save that filter for later (since > they can be complex), I'd like to store it in the database. Since the > values of the filter don't change, I don't see a problem with saving the > Example class. I did figure out that I could serialize the Example class > and store that in the database, and unserialize it when I want to use it, so > that is probably the best option for now. > > > > On Mon, Feb 25, 2008 at 8:49 AM, Jeff Butler <[EMAIL PROTECTED]> > wrote: > > I assume you are talking about the Abator example classes. But this isn't > exactly an Abator issue. > > > > iBATIS dynamic SQL is resolved at run time based on the values in the > parameter object - so you'd need to capture the SQL after the resolution > step and save it somewhere. You could probably do this by tinkering with > iBATIS internals, but the easiest way to do it would be to create a custom > logger and grab the SQL from the log. > > > > Another alternative would be to serialize the example class as you've > suggested - but this doesn't save the SQL, it only saves the values in the > example class - which would generate the same SQL on reuse. > > > > Is this some kind of a user preference or user history thing? > > > > Jeff Butler > > > > > > > > > > > > On Sun, Feb 24, 2008 at 4:02 PM, Ryan Shelley <[EMAIL PROTECTED]> > wrote: > > I'd like to be able to save the WHERE clause generated by the Example > classes in a database. The purpose is so that I can allow users to create > custom filters which distill down to SQL criteria, and then save them for > re-use later. I'm curious if anyone else has had a similar requirement, and > whether they attempted to serialize the Example object to XML, or if they > attempted to capture the generated SQL in another SQL statement. Any > thoughts? Thanks! > > -Ryan > > > > > > > > > >
