AFTER supported y/n?
-
- Registered User
- Posts: 376
- Joined: Fri Jun 18, 2004 10:58 pm
- Location: Girona, Catalunya (Spain)
- Contact:
Re: AFTER supported y/n?
Ah, there will probably be a good oportunity to scan all MODs for this kind of issues ...when Olympus...
-
- Former Team Member
- Posts: 90
- Joined: Wed Feb 09, 2005 12:21 am
Re: AFTER supported y/n?
If someone tries to run an SQL query with a reserved word in it, the query will still be parsed, but an error will still be thrown, none-the-less.
Also, if someone has a query with TYPE=MyISAM, it'll be removed and a warning will be thrown.
Why not do the same thing with AFTERs? Parse the query but throw a warning? It seems like throwing a warning would be just as effective at getting people to write good SQL queries as halting the conversion would.
Alternatively, it seems like a more meaningful error message could be made when AFTER is used. Perhaps the justifications made in this thread could be given when an ALTER TABLE containing an AFTER is used?
Also, if someone has a query with TYPE=MyISAM, it'll be removed and a warning will be thrown.
Why not do the same thing with AFTERs? Parse the query but throw a warning? It seems like throwing a warning would be just as effective at getting people to write good SQL queries as halting the conversion would.
Alternatively, it seems like a more meaningful error message could be made when AFTER is used. Perhaps the justifications made in this thread could be given when an ALTER TABLE containing an AFTER is used?
-
- Registered User
- Posts: 376
- Joined: Fri Jun 18, 2004 10:58 pm
- Location: Girona, Catalunya (Spain)
- Contact:
Re: AFTER supported y/n?
hmm... I may try to improve the parser so it generates more understandable warnings/errors. That's not easy though. Look for example the errors reported by MySQL itself "You have an error near ...".
However, these things should be detected by MOD authors in the first place, so they may have more knowledge to diagnose why their MODs don't work as expected, etc.
However, these things should be detected by MOD authors in the first place, so they may have more knowledge to diagnose why their MODs don't work as expected, etc.
Re: AFTER supported y/n?
I didn't comment your decision before as I fully respect it, but you know I'm quite sure nearly 100% of MOD authors have no clue if an equivalent of AFTER exist for Postgres, Access or MSSQL, and I'm quite sure too nowhere the phpBB group ask not to use AFTER. So nothing will be detected, as they don't care about use AFTER or not.markus_petrux wrote: However, these things should be detected by MOD authors in the first place, so they may have more knowledge to diagnose why their MODs don't work as expected, etc.
But now we know, it's not that important (even if personally I would have preferred to have the possibility to use it, even if for an other database the fields are added at the end of the table), so that's fine
Eternal newbie
-
- Former Team Member
- Posts: 90
- Joined: Wed Feb 09, 2005 12:21 am
Re: AFTER supported y/n?
Authors who've submitted their MODs for validation (atleast in the past few months) and whose SQL queries use AFTER usually get comments from usI'm quite sure too nowhere the phpBB group ask not to use AFTER. So nothing will be detected, as they don't care about use AFTER or not.