I did the refactoring on a Linux desktop. Of course I may have turned of case sensitivity sometime in the distant past, so I can't be certain it won't be a problem. If it turns out case is still an issue I would personally prefer that the case of the table match the case of the component.
Blair On Tue, Sep 28, 2010 at 1:12 PM, Michael Sharman <[email protected]> wrote: > I have a farcry 5.2.7 project which I've upgraded to 6.1 but have > noticed that a lot of the table names have changed case from what they > were previously (after updating the coapi). > > Tables like: > dmarchive (was dmArchive) > dmevent (was dmEvent) > etc > > We've previously had a few issues with database table names as we run > on Linux, I'm on a mac at the moment so I can't do a test yet. My > question...is this correct? Is there a naming "convention" for > database tables, at least the core ones? I have a funny feeling if I > ran this on linux it would fail. > > Should the naming convention be headless camel case; so dmImage > instead of dmimage etc? Same for any far** prefixed tables. > > Thanks. > > -- > You received this message cos you are subscribed to "farcry-dev" Google > group. > To post, email: [email protected] > To unsubscribe, email: > [email protected]<farcry-dev%[email protected]> > For more options: http://groups.google.com/group/farcry-dev > -------------------------------- > Follow us on Twitter: http://twitter.com/farcry -- You received this message cos you are subscribed to "farcry-dev" Google group. To post, email: [email protected] To unsubscribe, email: [email protected] For more options: http://groups.google.com/group/farcry-dev -------------------------------- Follow us on Twitter: http://twitter.com/farcry
