Well, I only use the web gui and openserctl, so I'm fine with it as it is.
However, I'm willing to implement/fix it if other users care. If you do, post
back and let me know.
Also, if any more features are wanted, list them here or put them on the
sourceforge site.
Mike
On Friday 11 August 2006 11:19, Norman Brandinger wrote:
I believe that phplib_id is only used by serweb.
There are a few
columns that fall into the category of being used only by serweb.
Recently the database creation scripts were updated to allow for serweb
tables to be created (or not created) based on user input, however,
there is no ability to specifically include or not include serweb
specific columns.
Perhaps, the roadmap can include a task to include serweb columns only
if serweb tables are being created.
So, Mike, my suggestion would be to keep the id column as a unique value
and only include phplib_id if you are going to support serweb (or want
to retain compatibility with the existing database creation/openserctl
scripts).
Any other comments, suggestions or opinions are welcome.
Regards,
Norm
Mike Williams wrote:
> That is definitely the issue, it's a known bug on sourceforge. I'm trying
> to think of a good fix.
>
> Here's what I sent to another user with the same reported issue:
>
> <<<
>
> As for openserctl failling, that is definitely something that I broke. In
> the database_tables.sql file, some modifications are made to OpenSER's
> tables, and dropping the column phplib_id is one of them. I replaced it
> with just 'id' because it was easier to work with in Ruby on Rails, makes
> more sense because it is not linked to any particular programming
> language, and because having an integer that can be autoincremented makes
> it much easier to manually work with in MySQL and to generate id's with
> no code, especially since the the former column was generated by PHP
> specific code.
>
> I'm not sure of the best way to fix the problem, as I'm not sure whether
> re-adding phplib_id would cause more problems or not. For one thing,
> there would need to be additional code in the interface, although this
> looks like it would be the only solution that would break nothing.
>
>
>
> What does the OpenSER team (and everyone else) think about the phplib_id
> problem?
>
> Mike
>
> On Friday 11 August 2006 10:25, Pat wang wrote:
>> Hi,
>>
>> Just managed to install the new openser administrator and everything
>> just works. Thanks to Mike for this nice application. However I can't
>> add user with openserctl anymore. The following error appears:
>> ERROR 1054 (42S22) at line 1: Unknown column 'phplib_id' in 'field
list'
>> ERROR: introducing the new user '5702' to the database failed
>>
>> On the other hand, adding new users from administrator GUI does not have
>> this problem. This happened right after installation of aministrator so
>> I think it is related to the administrator mysql table changes.
>>
>> Any suggestions please? Thanks,
>>
>> Patrick
>>
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users(a)openser.org
>>
http://openser.org/cgi-bin/mailman/listinfo/users
>
> _______________________________________________
> Users mailing list
> Users(a)openser.org
>
http://openser.org/cgi-bin/mailman/listinfo/users