Hi Wiliam,

You will regret it if you take that path.  See if you can't (A) use
one of the free development ones:-
http://otn.oracle.com/software/products/oracle9i/index.html
or (B) get your test machine to connect to the real Oracle (using a
test schema or database maybe).  Your main problems will be with dates
and date calcs - but the worst part will be you and your development
people missing out on the Oracle skills they're going to accumulate
during development - you know - those intangible things like "why did
it take 10 times longer when I did it that way..." kinda stuff.

Chris


Friday, February 6, 2004, 4:25:44 AM, you wrote:

WS> Hi

WS> I'm going to be working on a Perl app using a database through the DBD 
WS> set of drivers. The end production machine will run Oracle for which 
WS> there is already DBD::Oracle.

WS> However, we don't have access to Oracle locally and wish to use a 
WS> replacement for the bulk of the development process before moving over 
WS> to the production servers.

WS> Because both databases can be accessed using the DBI divers then it 
WS> would seem logical that the same application, if coded correctly, could 
WS> be used with a number of databases without changing much, if any, of 
WS> the code. This is the theory I'm working with.

WS> However, I know in reality that small changes to SQL syntax will have 
WS> to be made.

WS> What I'm basically asking is, what is the best database to use as a 
WS> development database before migrating over to Oracle? Is MySQL the most 
WS> similar in terms of syntax? Or can I stick with my preferred choice of 
WS> Postgresql? Are there any big gotchas to watch out for switching 
WS> between both databases or if I stick to fairly standard SQL syntax and 
WS> functions I should be OK. If there is a list of differences between the 
WS> functions of the various DBI drivers that would be great.

WS> Thanks for your help.

WS> Wil
WS> --
WS> Wiliam Stephens

WS> FBA MEDIA

WS> Tel: 01970 636412
WS> Mob: 07968 325637

WS> http://www.fbagroup.co.uk/

Reply via email to