Hi Frank
> IIRC (it's a while since I last stepped through this code), the > problem is that we the default value entered in the UI is stuck in the > higher layers. We remember it in the ODB file (as part of the column > settings), but we never pass it to the driver. > > Thus, the default value is "lost" before any SQL statements are > generated and sent to the driver. So that's why there is no "default ..." in the trace output. Since no default value is passed to the driver it is never put it into any statement. I could verify that, by looking at the corresponding variables in the driver, which seem to be empty all the time. > I don't remember the exact details, but there was something why a fix > wasn't as easy as just passing the value down to the driver. Would > need some time to investigate the relationship of the various default > values ... Do we already have an issue for this? There is no issue for this, because I wanted to get sure that this is problem is not related to our driver. Since I couldn't reproduce the behavior with MySQL today, but only with Ingres I'm not quite sure about that. On the one hand the default values are not saved by the driver to .odb, are they? On the other hand I couldn't reproduce it with MySQL. The exact behavior of OOo/Ingres is like this: The default values are saved properly when I create a new table. If I try to change the default values in an existing table only the default value of the last column of the table is changed successfully. Moreover this doesn't seem to be saved to the .odb, as the default values are reset when the connection is closed and reopened. Any suggestions what would be a good start for digging further into this? Best regards, Micha --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
