Subject | Changing column from not null to null |
---|---|
Author | lowhs2001 |
Post date | 2003-12-08T03:10:38Z |
Hi all,
I've this problem of changing a not null column to null can only be
recognise for new connection ( For super server, only after restart ).
Upon further investigation, it seems like this not null to null
update can only be done through direct update to system table ( I'm
using IBExpert to perform this ) and system table is cache by the
server. For super server, the problem is even more worse as system
table cache won't be refresh until the server is restarted.
So, is there any way to ask the server to refresh the system table
cache so that this kind of changes would be recognised immediately (
I'm using SuperServer now :( ) ?
thanks.
Regards,
Low
I've this problem of changing a not null column to null can only be
recognise for new connection ( For super server, only after restart ).
Upon further investigation, it seems like this not null to null
update can only be done through direct update to system table ( I'm
using IBExpert to perform this ) and system table is cache by the
server. For super server, the problem is even more worse as system
table cache won't be refresh until the server is restarted.
So, is there any way to ask the server to refresh the system table
cache so that this kind of changes would be recognised immediately (
I'm using SuperServer now :( ) ?
thanks.
Regards,
Low