Kostas Botsas
Kostas Botsas
Confirmed it's still an issue with v0.11.19
Note: this issue surfaced since IntelliJ version 2023.3, it doesn't occur with 2023.2.
Depends on https://github.com/xataio/xata/issues/1942
Tried it out, some feedback: with the existing table schema having brokerage as link, the CLI suggests to remove the link column (brokerage) ``` id,licenseNumber,licenseHolderName,licenseType,stateLicenseType,brokerage,licenseExpirationDate,address1,address2,city,county,zip,state 1,license1,name1,type1,state1,broker1,2023-07-10T16:04:33.932152Z,addr1,addr2,ny,us,16232,california ``` ``` xataCli import...
We can provide a hint to use the flag `keep-existing-columns` in this warning message then?
The same type issue applies not just to aliased but to the reverse linked table records ``` const record = await xata.db.ShoppingCarts.select([ { name: "