Hello,
I am not a full time developer, but would like to become more serious about becoming one. I have used Alpha versions 8-10 and have purchased V11.
After reading many of the posts on these forums regarding the decision to develop for the web using the DBF backend or some flavor of SQL for the backend I'm 90% sure I'm going to go the SQL route. (Probably MYSQL) I see the many reasons that argue positively toward an SQL backend path. (speed, scalability etc...). I am willing to learn different ways to do things and some SQL commands.
The last question I have that I haven't seen raised about this subject is the following:
Is there any reason(s) to NOT use a SQL backend?
(other than some amount of added complexity and perhaps it's overkill to use SQL for smaller, simpler applications with smaller amounts of data and fewer users)
To expand the question:
Any features of Alpha5 V11 that are not available or don't work when the backend is SQL?
Any aspect of the xbasic language that is significantly different or not available when the backend is SQL?
Any aspect of the built-in security system that is significantly different or not available when the backend is SQL?
Any changes to action scripting?
Are any features and properties of grids and dialogues no longer available if backend is SQL?
etc...
Any web components that no longer work?
Do we still create sets?
Another way to pose this question: Does Alpha5 itself, the program not the company, care what the backend database is?
Thanks to all who have commented on this issue so many times before. I'm not really looking for super detailed responses to all these expanded questions much beyond yes or no. If all the answers are no i can proceed with SQL if many are yes than I need to dig deeper to see what the changes are and then decide.
Kevin
I am not a full time developer, but would like to become more serious about becoming one. I have used Alpha versions 8-10 and have purchased V11.
After reading many of the posts on these forums regarding the decision to develop for the web using the DBF backend or some flavor of SQL for the backend I'm 90% sure I'm going to go the SQL route. (Probably MYSQL) I see the many reasons that argue positively toward an SQL backend path. (speed, scalability etc...). I am willing to learn different ways to do things and some SQL commands.
The last question I have that I haven't seen raised about this subject is the following:
Is there any reason(s) to NOT use a SQL backend?
(other than some amount of added complexity and perhaps it's overkill to use SQL for smaller, simpler applications with smaller amounts of data and fewer users)
To expand the question:
Any features of Alpha5 V11 that are not available or don't work when the backend is SQL?
Any aspect of the xbasic language that is significantly different or not available when the backend is SQL?
Any aspect of the built-in security system that is significantly different or not available when the backend is SQL?
Any changes to action scripting?
Are any features and properties of grids and dialogues no longer available if backend is SQL?
etc...
Any web components that no longer work?
Do we still create sets?
Another way to pose this question: Does Alpha5 itself, the program not the company, care what the backend database is?
Thanks to all who have commented on this issue so many times before. I'm not really looking for super detailed responses to all these expanded questions much beyond yes or no. If all the answers are no i can proceed with SQL if many are yes than I need to dig deeper to see what the changes are and then decide.
Kevin
Comment