![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
|
I am using the ASA 9 with latest EBF 1250. Sybase Central is 4.2.0.2047. This evening i have been working for about 10 hours only altering or creating new procedure or functions (P/F). There have to be a very serious bug in the way SC saves its P/F because I have lost changes at least a dozen times this evening. Luckily I have have a routine to save the P/F to file before I close the P/F window. I know that if I just go and save P/F to file before with the Save file as changes will not be saved to the database. But I know I have saved the P/F with either Ctrl + S, the save button on the toolbar or the Save procedure on the File menue. It is also bad behaviour that if we have done a lot of changes to a P/F and goes to the File menu and select Save File As. Then after that is done if I closes the window I will not be prompted with a message to save to the database. This is realy bad and have cost me several hours this evening. Another bug that is not serious, but irritating is that every time I select the File->Save File As it does not remember the last folder I used. --- Kjetil --- kjetil.valoy (AT) iticket (DOT) no |
#2
| |||
| |||
|
|
My reply is inline below. I have posted a message last week about the SQLSTATE S1003. It seams that nobody wants to answer me. Do you know someone that could care? --- Kjetil --- On 15 Dec 2003 19:34:35 -0800, "Rich Jones" <richj (AT) sybase (DOT) com> wrote: I see two issues here: 1. Saving multiple times when editing in a new window does not work: This was an issue that was fixed in EBF 1235. Previously, if you edited a procedure, trigger, view or event in a new window by selecting the item in the left or right pane and then selecting File -> Edit in New Window, then only the first set of changes would be saved. That is, if you saved your changes to the database, made more changes, and then saved to the database again, then the second set of changes would be lost. Actually, what happened was the first set of changes would be saved in the database again. You indicate that you are running EBF 1250, but it sounds like you might still be experiencing this problem. Can you try the above steps and let me know if your second set of changes are saved to the database? It updatet ok. I could not provoke SC to not save the changes. I wonder if the issue can be related to the Save File As; that I have used it but forgot to use the Ctrl + S. But I think I had tired at least one of the P/F changes. It is not easy to say if my test is realistic. I often work with a lot of P/F windows open and can have them open for hours and save dozen times. One pitfall I noticed is that if you push Ctrl + E (to get the P/F in a separat window ) for at P/F that allready is in a separat window it lanches a new window with the same procedure. It could bee good with a warning stating that this P/F allready is loaded in a separat window. If so, good; if not, either the EBF install did not succeed or there is still a bug here that I can't reproduce. 2. Saving to a file marks the editor's contents as unchanged, so closing the editor does not ask you whether you want to save the changes to the database. This is obviously wrong. Saving to a file should behave like a "Save a Copy As..." command and not mark the editor's contents as unchanged. I will fix this. Thank you! In addition, I'll look into retaining the editor's current directory for all editor windows in a session. Note that the setting is currently retained for each editor until you close the editor window, but I agree that when using multiple editors, this is not enough, since you need to set it for each editor window. Thank you very much !!! Rich "Kjetil Valøy" <__no_spam__kjetil.valoy (AT) iticket (DOT) no> wrote in message news:3fde562c.280666527 (AT) forums (DOT) sybase.com... I am using the ASA 9 with latest EBF 1250. Sybase Central is 4.2.0.2047. This evening i have been working for about 10 hours only altering or creating new procedure or functions (P/F). There have to be a very serious bug in the way SC saves its P/F because I have lost changes at least a dozen times this evening. Luckily I have have a routine to save the P/F to file before I close the P/F window. I know that if I just go and save P/F to file before with the Save file as changes will not be saved to the database. But I know I have saved the P/F with either Ctrl + S, the save button on the toolbar or the Save procedure on the File menue. It is also bad behaviour that if we have done a lot of changes to a P/F and goes to the File menu and select Save File As. Then after that is done if I closes the window I will not be prompted with a message to save to the database. This is realy bad and have cost me several hours this evening. Another bug that is not serious, but irritating is that every time I select the File->Save File As it does not remember the last folder I used. --- Kjetil --- kjetil.valoy (AT) iticket (DOT) no |
![]() |
| Thread Tools | |
| Display Modes | |
| |