On Thu, Feb 19, 2009 at 10:39 AM, Tim Perrett he...@timperrett.com wrote:
Just to update this thread - Derek has been a super star and fixed the
schemifier so now it doesn't bone on application boot. Result.
Thanks Derek.
Rock on Derek!
Tim
On Feb 12, 8:02 pm, Tim Perrett
Glad I could help!
On Thu, Feb 19, 2009 at 11:40 AM, David Pollak
feeder.of.the.be...@gmail.com wrote:
On Thu, Feb 19, 2009 at 10:39 AM, Tim Perrett he...@timperrett.comwrote:
Just to update this thread - Derek has been a super star and fixed the
schemifier so now it doesn't bone on
Just found a bug with the MSSQL drivers... Looks like its all working
fine, but on boot I see this with the schemifier:
Like I say, it works (the app that is) but having this stack trace on
boot is not nice. Any ideas?
INFO - CREATE TABLE modifiers (name VARCHAR(100) , id BIGINT IDENTITY
NOT
The defaultSchemaName fix for the SqlServerDriver is checked in.
Please let me know if that fixes the startup stacktrace you were
seeing.
On Feb 12, 6:48 am, alm4x1...@gmail.com alm4x1...@gmail.com wrote:
I have some patches to Schemifier that were not ready by the 1.0
freeze.
I tracked this
Al,
It would be usefull if you could just post an example of the needed
connection object that people will need to put in boot.scala
Cheers
Tim
On Feb 11, 8:59 pm, alm4x1...@gmail.com alm4x1...@gmail.com wrote:
Hi All:
I've added support for Microsoft SQL Server and Oracle 10g JDBC driver
