Rocket
Posts: 45
|
| Posted: 12/04/2010, 10:42 PM |
|
I'm quite sure this is a stupid rookie issue, but I really need help.
I've a project that I'm getting happier and happier with - the help in here has been great, the ideas and other posts have really helped alot.
BUT (ya know this was commin...), I am making changes to my MS SQL 2K5 db to add new/missing abilities to this project - mostly because I am seeing some of the awesome things this bad boy can do. The unfortunate part is that when I make these changes (could be a data type or dropping/adding a column). This really pooches things and I've gotten used to fixing things and that is fine, but it's tedious and time consuing. Thanks god for realtime view - that really helps.
Is there something that I am missing or can do so as to help minimize these issues. I realize that good db design is paramount, unfortunately that is not always the case and changes are always needed.
I think I'm spoiled by using ASP runner which allows one to sync the db. But that is in the past, going forward, any suggestions would be greatly appreciated.
cheers...
|
 |
 |
Rocket
Posts: 45
|
| Posted: 12/08/2010, 6:36 PM |
|
This forum displays an indication that Jan van Dalen replied to this post (it says 1 reply with Jan's anme).
i can't see the post???
Rocket
|
|
|
|
andrewi
Posts: 162
|
| Posted: 12/09/2010, 10:17 AM |
|
Yes, I noticed there was a phantom post too.
With regard to your question, I don't know what else CC could reasonably do. If you're making great changes to your database schema, then you're going to have to do some work in the front end app. Would you really want CC to delete a column from your grid form if you dropped the related data column? If you change a datatype, CCS could propagate the changes to the forms - but then, what if you had custom code based on that field; that would still have to be corrected manually. Perhaps you might have wanted to display a boolean field as an integer for some reason - so don't want CCS updating the field type behind the scenes. Automatic updating might be a very mixed blessing; I can only just put up with the way CCS automatically rearranges the HTML and Javascript!
I suppose one thing you could do is put a layer between codecharge and your database design. You could write stored procedures for regularly used lists (e.g. combobox sources), and forms. Then if you change one of the source table structures, you just have to edit the stored procedure. The dozen grids you have using the stored procedure needn't notice any difference... There's some overhead of work there, but if the ratio of forms to tables is high and the changes regular enough, it might make sense. (and there are other benefits, such as securitym to using sp's)
|
|
|
|
Rocket
Posts: 45
|
| Posted: 12/09/2010, 2:14 PM |
|
Quote andrewi:
Yes, I noticed there was a phantom post too.
With regard to your question, I don't know what else CC could reasonably do. If you're making great changes to your database schema, then you're going to have to do some work in the front end app. Would you really want CC to delete a column from your grid form if you dropped the related data column? If you change a datatype, CCS could propagate the changes to the forms - but then, what if you had custom code based on that field; that would still have to be corrected manually. Perhaps you might have wanted to display a boolean field as an integer for some reason - so don't want CCS updating the field type behind the scenes. Automatic updating might be a very mixed blessing; I can only just put up with the way CCS automatically rearranges the HTML and Javascript!
I suppose one thing you could do is put a layer between codecharge and your database design. You could write stored procedures for regularly used lists (e.g. combobox sources), and forms. Then if you change one of the source table structures, you just have to edit the stored procedure. The dozen grids you have using the stored procedure needn't notice any difference... There's some overhead of work there, but if the ratio of forms to tables is high and the changes regular enough, it might make sense. (and there are other benefits, such as securitym to using sp's)
Thanks andrew. My bad, I wasn't suggesting that CCS should do anything, what I was more intetested in was how to sync, "Manually" is where I was trying to go, but apparently I didn't go there.
I totally agree, I wouldn't want to muck up code because I deleted (or added a column). More than likely it's still newbie pains. The issues that I am running into are more with respect to migrating an existing ASP runner app. This thing has so many good things that we were loiking for and as a result we can see things that we wantd in our DB from the get go and now we can do so.
I just had a pretty lengthy meeting with some of my developers and we have come to the realization that a redesign is in order. This will minimize these types of questions, and I appolgize if I inferred that CCS4 should take care of everyting - of course it can't.
I've found this to be an extremely powerful forum and the knowledge and experience in here is pretty tremendous, I suppose I was looking for a trick or SIX that someone had come up with in this instance.
Thanks again for your valued imput.
Cheers.
|
|
|
|
|
