SQL Server Query not returning results

Wappler General Need Help
41

Yes dbo prefix will work just fine. With Ms sql first part before the table name is considered the schema.

That is why it should be always tge schema name to avoid ambiguity.

42

Hi,
I did some testing and confirmed that Wappler does not support periods (’.’) within a table name. Any schema name works correctly e.g. ‘dbo’ or ‘Invoice’. Wappler will recognize the ‘dbo.’ but any other period after that will cause a query to fail.
So ‘dbo.TestTable’ will work, but not ‘dbo.Test.Table’.

Unfortunately this is a deal-breaker for me as I have 140+ tables which use periods in their names. I cannot change the names without breaking many years of code and reports which function perfectly with the periods (Visual Studio, Linq-to-Entities and data models, MS Access reports).

Thanks for the help, I really do appreciate it and hope it may help anyone else with this issue.
Speed

43

It’s really not a good practice to use dots in the database table names, and that’s not a Wappler requirement.

1 Like
44

Teodor,
There is no best practice regarding using periods in table names. To each their own.
Wappler does have a requirement here though: no periods in table names.
Ten days ago I posted a screen shot which clearly showed the table name with periods. It took days before anyone even noticed it (patrick). This may be because it has never come up before, and I get that. In fact, I may have contributed to saving another Wappler user’s time if this issue ever comes up again. Makes me feel a bit better to think it may have been helpful.
It’s easy to comment now about good practice but this comes across as condescending to customers and is not helpful to anyone. And again, it took Wappler staff days before they noticed the problem and they are the experts in Wappler, not me. The priority for any business should be to help resolve an issue as this will bring Wappler more business and increase potential customer’s confidence in the product. I would urge you to try and see this issue from my point of view–a paying customer.
As far as how Wappler could avoid this issue in the future, I can’t say. But I think we can all agree that lecturing or arguing with a paying customer is not good business.
HTH

46

Although not considered good practice, we will investigate if we can support dots in table names specially for Ms SQL in the future.

47

More reading why you shouldn’t use dots in table names:

1 Like