fpSql

[ernieb]

I for one would like to see a fully functional fpSql product. One that I would not need any of the filePro development tools at all. I want the ability to create tables, update, add and delete records just as I do with mySql.
We are moving more and more into web based applications and fpCgi and XML aren't enough.

[kencole]

I for one would like to see a fully functional fpSql product. One that I would not need any of the filePro development tools at all. I want the ability to create tables, update, add and delete records just as I do with mySql.
We are moving more and more into web based applications and fpCgi and XML aren't enough.

Such a facility would have to include a users/permissions table as I would not want any/all users to have all of these capabilities.

I like fpSQL now since I can give it to SQL savvy users, and we have plenty, and they can retrieve data all day long without deleting/changing it which I cannot stop with *report.

[ernieb]

I for one would like to see a fully functional fpSql product. One that I would not need any of the filePro development tools at all. I want the ability to create tables, update, add and delete records just as I do with mySql.
We are moving more and more into web based applications and fpCgi and XML aren't enough.

Such a facility would have to include a users/permissions table as I would not want any/all users to have all of these capabilities.

I like fpSQL now since I can give it to SQL savvy users, and we have plenty, and they can retrieve data all day long without deleting/changing it which I cannot stop with *report.

Yes there would be a definite need for user/permission table - but I would be happy with the functionality and forcing me to control permission for now. I'm using PHP now and validate at login. I could easily restrict those without 'write' permissions to only 'readonly' queries and/or pages.

[kencole]

Yes there would be a definite need for user/permission table - but I would be happy with the functionality and forcing me to control permission for now. I'm using PHP now and validate at login. I could easily restrict those without 'write' permissions to only 'readonly' queries and/or pages.

That is fine for controleld use via CGI/Perl/PHP etc but not for CUI users, of which I have many.

We currently have a web front end for fpSQL that allows users to enter variable data, run the query, display the results back in the browser and optionally load into Excel, an actual Excel spreadsheet, not fixed field lenght or CSV.  Currently IT writes the query or stores user queries.  I was hoping to extend this to a graphical "write a query" but would be loath to if the users had create/delete/modify capabilities.

[ernieb]

Yes there would be a definite need for user/permission table - but I would be happy with the functionality and forcing me to control permission for now. I'm using PHP now and validate at login. I could easily restrict those without 'write' permissions to only 'readonly' queries and/or pages.

That is fine for controleld use via CGI/Perl/PHP etc but not for CUI users, of which I have many.

We currently have a web front end for fpSQL that allows users to enter variable data, run the query, display the results back in the browser and optionally load into Excel, an actual Excel spreadsheet, not fixed field lenght or CSV.  Currently IT writes the query or stores user queries.  I was hoping to extend this to a graphical "write a query" but would be loath to if the users had create/delete/modify capabilities.

I am definitely not in disagreement here - but 'any' additional functionality would be appreciated. Yes - it would be nice to see an 'fpsql_connect' and validate users as mySql does - but I would venture a guess that would delay the functionality by a considerable time frame. XML has been discussed for somewhere around 4 years. I'm just saying 'baby steps' to get functionality out to the developers would satisfy me for now.

[ernieb]

I wish when I use 'SET LINES 0' and 'SET OUTPUT filename' that fpSql would honor field lengths and not field Name lengths. Sure would make the import routines easier, since I know the lengths of the fields.

[kencole]

Yep, run into that little catch on a regular basis.

Ken

[ernieb]

It would be nice if fPSQL had the ability to 'remove' a saved query as we don't allow our users shell access.