Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 3 of 3 total |
b15 issue |
Mon, Jun 28 2010 12:42 PM | Permanent Link |
Hershcu Sorin | Hello
I shift to edb V2.03b15. I have a table with an incremental field defined as generated not null. When I perform ApplyCachedupdates it's raise the error "can't save the field with null value" I shift back to b14 and it's run ok. Thanks Sorin |
Mon, Jun 28 2010 6:53 PM | Permanent Link |
Charalampos Michael | Dear Sorin,
> I shift to edb V2.03b15. > I have a table with an incremental field defined as generated not null. > When I perform ApplyCachedupdates it's raise the error "can't save the field > with null value" > > I shift back to b14 and it's run ok. It's a bug and should be fixed in the next build. -- Charalampos Michael - [Creation Power] - http://www.creationpower.gr |
Sat, Jul 3 2010 9:58 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Sorin,
<< I have a table with an incremental field defined as generated not null. When I perform ApplyCachedupdates it's raise the error "can't save the field with null value" >> The next build 17 will have a fix for this. There has been some issues with the IDENTITY columns being used with cached updates in the past few builds, and this will finally resolve them. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Saturday, April 27, 2024 at 08:52 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |