Hi Frank, > Hmm - you couldn't reproduce the default values vanishing, or you > couldn't reproduce the default values not being passed to the driver?
I couldn't reproduce the vanishing. The defaults were saved correctly when connecting via the SDBC-JDBC bridge to MySQL or via OOo's MySQL driver. However, when connecting to Ingres via the SDBC-JDBC bridge or using my driver the vanishing appears. Playing around with the drivers a bit more I also recognized folloing: When changing default values and using OOo/MySQL the method OMySQLTable::alterColumnByName is not even called, which makes sense as this doesn't require to execute anything on the database, but when using OOo/Ingres OIngresTable::alterColumnByName is called. > Sounds a little bit like there lingers another bug somewhere ... > > The table designer is in dbaccess/source/ui/tabledesign. Saving a > changed design is centrally done in OTableController::alterColumns - > this is where I would start. > > For the various column classes involved ... I'm not sure which of the > ones in dbaccess/source/core/api would be the best to start with (Ocke > would be able to answer this more precise, but he's still on > vacation), > I suggest you simply touch every file with "column" in its name, and > every file which a "grep DEFAULT *" mentiones, build them with > "debug=1", and let the debugger guide you, starting from the > aforementioned alterColumns method. Thanks for this. I will try get further from there. Best regards, Micha --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
