Sorry, hit send before finishing my email. The migrations will be odd because the earlier ones will fail to load on Oracle because of the reserved words, where the later migrations will expect the tables and columns to be there so they can be changed. I don't have a good idea for how to work around that issue. Any one else?
On Wed, Nov 19, 2008 at 4:04 PM, Carl Fyffe <[EMAIL PROTECTED]> wrote: > Honestly, it would be better to come up with a solution similar to the > one used for tables, where the columns are changed globally. It might > be easier to just change the column names but that will make the > migrations... odd. > > On Wed, Nov 19, 2008 at 2:52 PM, Jason Sears <[EMAIL PROTECTED]> wrote: >> Yes, the issue is the reserved words used for column names, specifically I >> found both size and comment. >> >> The blog post does look like a solution on first read. I'll see where it >> takes me when I attempt to apply it. >> >> I will say the blog appears to assume the table structure is in place with a >> prefix value while the Model is created without a prefix. My question now >> becomes "How do I extract DDL from the model?" If this is a common question >> or process I apologize. >> >> Thanks for the quick and relevant responses, this is a very helpful >> community. >> >> Thanks, >> Jason >> >> On Wed, Nov 19, 2008 at 8:42 AM, Levi Rosol <[EMAIL PROTECTED]> wrote: >>> >>> I'm not sure that solves his issue though. That gets around the table name >>> issue, but for columns, Oracle is way more picky than both MySQL and MS SQL. >>> >>> Could something similar be done, but for column names? >>> >>> I just did some quick research on this and found this blog post. will this >>> work for you? >>> >>> >>> http://kusar.org/wordpress/2008/05/07/adding-in-a-legacy-lookup-database-in-rails/ >>> >>> >>> Levi Rosol >>> >>> >>> >>> >>> On Wed, Nov 19, 2008 at 8:06 AM, Carl Fyffe <[EMAIL PROTECTED]> wrote: >>>> >>>> Jason, >>>> >>>> Give this a try. You can prefix your table names for all tables. By >>>> doing that you should get around any naming issues. In your >>>> environment.rb add the following: >>>> >>>> Rails::Initializer do |config| >>>> config.table_name_prefix :oracle_sucks >>>> ## other fun configurations >>>> end >>>> >>>> Just kidding about the prefix by the way... I thought I would toss my >>>> joke in the ring too... :-) I would use something very short like os, >>>> or just o to ensure I didn't bump into Oracle's name length limit >>>> which I think is 32. >>>> >>>> Hope that helps, let me know if it works. Oracle is in my future as well. >>>> >>>> Carl >>>> >>>> On Tue, Nov 18, 2008 at 11:07 PM, Jason <[EMAIL PROTECTED]> wrote: >>>> > >>>> > I am new to RoR and CommunityEngine so I may be well off base on my >>>> > approach. Has anyone worked through deploying CommunityEngine with an >>>> > Oracle database backend? >>>> > >>>> > I have started down the path and found there to be a number of tables >>>> > with reserved words as columns. >>>> > >>>> > So far I've found columns named "size" and "comment" which are >>>> > reserved. I am considering tweaking the code but feel this will >>>> > compromise my ability to upgrade. >>>> > >>>> > Any suggestions? I know the easy answer, "don't use Oracle" and it's >>>> > on the list but I'm interested in integrating into some other >>>> > applications running in Oracle. >>>> > >>>> > Thanks, >>>> > Jason >>>> > >>>> > > >>>> > >>>> >>>> >>> >>> >>> >> >> >> >> >> > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CommunityEngine" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/communityengine?hl=en -~----------~----~----~----~------~----~------~--~---
