Sigh. You are still missing the point.
The table editor is there specifically for you to add new columns to your tables and Links SQL is setup to be able to utilize the new columns you add, Links SQL was set up to be flexible and suitable for almost every type of scenario.
The irony is that what you are suggesting is inflexible and constricting. You simply need to use $DB->editor and $DB->creator to create and manage new columns and the default columns should not be touched.
That is how myself and Yogi and every other plugin author writes their plugins and that is how you should do it too. You really need to listen to people with more experience than yourself, especially Alex who has already suggested to add new columns.
Like I've said a few times, this is what it _really_ boils down to. It is not suitable for *you* and you are unwilling to make an effort to find an alternative route. I'm sure plenty of things are not suitable for me too, but I work with what I have and there is almost always a different route I can take which doesn't involve me asking Alex to re-write code.
I guarantee I could write a plugin that does what you want without Alex needing to change anything.
I'm sure you'll start telling me I'm horrible and mean but the reason I'm getting really annoyed here is because I can see what direction your plugin is heading and it isn't the right direction and I'm only trying to help you get back on track.
If you still insist that Alex re-writes the code (I'd be _very_ surprised if he did)....then I guess we have all been wasting our breath and I will put my energies elsewhere.
The table editor is there specifically for you to add new columns to your tables and Links SQL is setup to be able to utilize the new columns you add, Links SQL was set up to be flexible and suitable for almost every type of scenario.
The irony is that what you are suggesting is inflexible and constricting. You simply need to use $DB->editor and $DB->creator to create and manage new columns and the default columns should not be touched.
That is how myself and Yogi and every other plugin author writes their plugins and that is how you should do it too. You really need to listen to people with more experience than yourself, especially Alex who has already suggested to add new columns.
Quote:
And current database is not suitable for meLike I've said a few times, this is what it _really_ boils down to. It is not suitable for *you* and you are unwilling to make an effort to find an alternative route. I'm sure plenty of things are not suitable for me too, but I work with what I have and there is almost always a different route I can take which doesn't involve me asking Alex to re-write code.
I guarantee I could write a plugin that does what you want without Alex needing to change anything.
I'm sure you'll start telling me I'm horrible and mean but the reason I'm getting really annoyed here is because I can see what direction your plugin is heading and it isn't the right direction and I'm only trying to help you get back on track.
If you still insist that Alex re-writes the code (I'd be _very_ surprised if he did)....then I guess we have all been wasting our breath and I will put my energies elsewhere.
