Hi everyone,
I installed wappler7 beta on my notebook and opened one of the latest projects I created to run some initial tests.
My first surprise was seeing that the old connection no longer works.
After a few attempts, I found out that you need to remove the part after the host IP address (in my case, I had to delete 'MSSQLSERVER2019').
I don't think it's a big issue.
Aside from that, after this I tried switching from 'AppConnect1' to 'Stable'
If I click 'yes' and save the page, everything seems fine. I tried debugging some queries and they seem ok.
I have two questions:
1-When switching from 'AppConnect1' to 'Stable', could I have problems with my projects, especially with my queries? As you saw, I use MSSQLServer on aspx pages.
2-Once I have switched from 'AppConnect1' to 'Stable', will this change inevitably affect all the projects I have in Wappler? I mean, could I keep one project with 'AppConnect1' and start a new one with 'Stable'?
At first glance, it doesn't seem so, since in the 'Project Assets Updater' of another project I opened after changing the 'Channel', I always see 'Stable' and it prompts me to do an 'Update'.
Could I say no? What would happen, apart from the fact that it would ask me every time I open the project?
Sorry if these are silly questions. My concern is what might happen when I switch to the new software and the new Channel, especially regarding malfunctions on old projects.
I hope I explained myself clearly. Thank you!!!
Yes, AppConnect was rewritten from scratch, it's now in version 2, but most of the bugs (if not all) have been fixed by now, it's unlikely you'll have problems.
No, AppConnect doesn't break queries like you shown in the screenshot.
No
Yes
Yes, you could say no, probably nothing bad would happen, but no guarantees
I would take a more cautious approach than @Apple …
My app is very large and complex, and it took me a significant time to fix all the issues that came up when going from v1 to v2. They provide the same functions but work very differently under the hood, potentially causing issues with timing of events, management of locally stored data, and S3 access at the very least.
I worked on a separate branch of code and did extensive testing of every function of my app before committing to v2 for production!
@Antony .... Im in the same boat as you .. have a very large project.. and as soon as i switch over to AC2 things break.. not because AC2 is broken.. but because how it functions...
As i have loads of "timing" events and count downers... and if I switch to AC2 it jus breaks my site.. .... so the saying goes.."if it ain't broke, don't fix it"... and i honestly cant see a "speed" increase.... So when i open up my project I just NEVER update ... and still use AC1.. and its still smooth as butter doing its thing.. And still editing in AC1...
But then again in using PHP... that might make things a bit easier....
true......... as the work around was to go and make loads of things in flows with a "wait" ... because of how the site was done... and AC2 being to fast.. .... ... it was just for that one project.. that I dont want to risk and redo.. maybe in a future life ,...
,...