I just read the Feedback entry and I read nothing (there is nothing to read) that said that in it.
?
Simple words about the documentation in API 2.0: take a look at SQLiteDATABase examples.
Go to the Sample Code part at the bottom of the text.
a. There is three examples: two of them, the file name is MyDB.sqlite
For the third, the file name is Employees.sqlite.
b. API 1 or API 2 ?
The third example uses API 1.
c. Example 1 creates a sqlite data base file,
Example 2 opens an existing data base file,
Example 3 adds a record to a table (using API 1).
Dont you think there is a missing entry here (between Example 2 and 3) ?
That example is in another page: how to add a TABLE in the data base file. But the example is not consistent with what found in the other page (specifically, the sql command string: TABLE name is different than above, same page and the main page)
http://documentation.xojo.com/api/databases/database.html#database-executesql
Joe Newbie will be completely lost.
LR goal is to make the reader (not to say the developer) comfortable / giving her/him solid examples
[quote=458566:@Emile Schwarz]I just read the Feedback entry and I read nothing (there is nothing to read) that said that in it.
?[/quote]
I know, but I really really would appreciate this feature, since I save always with “save as” giving the binary or xml version a unique name (last edit or build no.) so the mechanism “show api 1.0 if project is saved with the same name” does not work for me, and I guess I’m not the only one doing this.
Hoped some more will spend some points, too 
I do not do that. Before starting to make changes, I made a copy of the project into a Project Backup folder.
I asked the question because you were as positive as you have first hand information this will be done.
Only believe what you get in your hands… An Entry in Feedback is a required “kick off”. Only once you see in in the ReleaseNotes of a (Pre)Release you can start being happy and start looking forward to it.
At least it’s a “Top 10 User Favorite”… let’s hope Xojo listens and respects their user’s needs (but… they can also just ignore it such as it happens with so many requests that are lying there for years…). 
Same happens with Apple, politics and almost everything nowadays. Looked at my Apple “Feedback” today, a bunch of bugs reported in Mojave betas, still haven’t been acknowledged or fixed. Here we are a year later, and my listed of unacknowledged/unfixed issues with Apple is Oh so much longer.
As for politicians…
I didn’t spend much time looking. I was so freaked out I put my computer to sleep and went to bed myself.
From what I recall the errors seemed to be largely FolderItem-related.
generally it i hard to tell as they are mixed into the depreciations and you cant find the wheat for the chaff.
[quote=458514:@Paul Rodman]I decided to try compiling my 2019r1 project in 2019r2.
545 errors and 55,173 deprecation warnings.
I think it’s time to rethink my development platform. Thankfully my licence expires in November.[/quote]
The only error I had came from a variable I had called Var (short for Variance).
My 4770 warnings is now down to 614. Most of those will be my date class and GetFolderItem.
11256 _ Loving to see the number decreasing slowly
You can please some of the people some of the time.
Props to the plugin devs who are staying on board.
I’ve tried to find a replacement for xojo, nothing exists in the RAD space that can compare (That I’m aware of).
I think I take it back that only Events really need to be reverted. After having played more with it then every single time I come to Arrays the code becomes unreadable and obscure code.
Example:
mColumns.Append
becomes
mColumns.AddRow
I have not found any case where AddRow actually looks right or makes your code readable. Except if your array is maybe Array of Rows.
During the beta more than a few of us argued strongly against using table terminology for arrays … Personally I think it will get Xojo ridiculed and it will be something used to dismiss it as non-professonal.
Obviously Geoff thinks otherwise.
-Karen
[quote=458781:@Derek Traxler]You can please some of the people some of the time.
Props to the plugin devs who are staying on board.
I’ve tried to find a replacement for xojo, nothing exists in the RAD space that can compare (That I’m aware of).[/quote]
If I might add, “I’ve tried to find a replacement for xojo 2019r1, nothing exists, include 2019r2”. Right now we will stay with 2019r1 since we can’t move to Catalina anyway because of some 3rd party apps that are only available in 32 bit. We will reassess at a later time.
Anyone have any experience with B4X?
Note that taking this conversation in the direction of other languages is a sure way to get it shut down.
Yeah, let’s not talk about competitors.
From my roughly 4.500 remaining deprecations over 900 come from m_string only.
I don’t intend to do anything about the deprecations at this point, but compatibility has been fixed in the recent update.
big issue for those who write and or use Xojo based custom controls etc. If you update those controls to R2, you shoot yourself in the foot, because now only those other developers who are only using R2 can take advantage.
@Kem Tekinay: I just wanted to whine and blame others. I didn’t have any compatibility problems with the version I was using.
@Dave S: and if you don’t update you get whining customers.