Kewl! I tried to quick test it but didn't have enough time. I'll be offline for the weekend, but will check it out asap. I'm not on the village mailing list but you may want to drop a note there about your changes, the author is here also so maybe he'll have some input. We also have the need for turbine/sybase functionality, but time has prevented us from messing with this too much. So this is great. Any help I can be, just let me know. l8r, jb "Rafal Krzewski" <[EMAIL PROTECTED]> wrote: [SNIP] > I snipped metadata access method calls from village/Column.java > and checked what is working and what is not. The good news > is that only getTableName is not implemented. All the other stuff > that village uses is working just fine. This means that creating a > schema for specific table WILL work, because you know the > name of the table you are processing, don't you? This also means > that QueryData for a statements with a JOIN clause, there is no > simple way of determining what table is specific column coming from. > But of course you can always parse the query... > > > If you really wanted to hack a > > way to use sybase with Turbine's default behavior, just hack > > Village to support it. > > Sure, why not!? :) You can find my patch enclosed at the end > of the message. > > It's transparent to the drivers that support > ResultSetMetaData.getTableName(int column); On Sybase, it will work > correctly in "Schema(table)" and "QueryDataSet(statement)" will have > bogus "statement" table name in all columns in it's schema. > This calls for another patch for turbine.om.peer.BasePeer.initTableSchema, > to use > "Schema(table)" constructor insead of duplicating it's functionality with > QueryDataSet. > The patch is also at the end of the message. > > I have little knowledge about OM's inner workings, and usage of schemes > througout > I, so it's hard for me to determine if schemes from > "QueryDataSet(statement)" are > important. At least, this simple patch lets Turbine run on Sybase. By the > way - > I discovered an error in the sql scripts I posted earlier - You cannot > update timestamp > columns under Sybase, therefore Visitor.LASTLOGIN must be changed to > datetime > type. A patch for that is on the very end of message. > > > Rafal [SNIPPED PATCHES] Jeff Brekke mailto:[EMAIL PROTECTED] http://sites.netscape.net/ekkerbj ____________________________________________________________________ Get your own FREE, personal Netscape WebMail account today at http://webmail.netscape.com. ------------------------------------------------------------ To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Problems?: [EMAIL PROTECTED]
