From: Ben F. <fa...@cs...> - 2005-07-20 19:45:54
|
After thinking about this a little more, it seems that SQL::T should keep true table comments separate from file comments. Maybe in addition to the table_comments section, you could have a table_file_comments and the same with field_comments. This could be pretty tedious to add to all the parsers and producers but it seems like the "right" thing to do. mwz On Wed, 2005-07-20 at 15:06, Chris Hilton wrote: > > > -----Original Message----- > > From: sql...@li... > > [mailto:sql...@li...] On > > Behalf Of Ken Youens-Clark > > Sent: Wednesday, 20 July, 2005 13:49 > > To: Fairy SQL > > Subject: Re: [sqlfairy-developers] Removing table comments > > from MySQL Parser [Attn. Chris] > > > > Maybe we should have a "no_comments" option for producers so > > this won't be a problem for you? But I'm still opposed to > > removing the comments. > > Any comment is part of the schema, IMO, regardless of how > > it's declared. > > I'm more of the opinion that if you feed it to the database and then > can't get it back out again, it's not actually part of the schema. But > I'd like to hear more about what others think; I can work with it either > way. > > Chris > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&opk |