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 -~----------~----~----~----~------~----~------~--~---
