Oracle is the worst database we have to deal with. It does not support
pagination. It does not support long names. It deals with BLOB in a
different ay then anything else.
Anyway, my advice is edit plugin_wiki and change the names of the tables to
make them shorter.
Or better. Do not use plugin_wiki. Most of the functionality is now in
auth.wiki() (although it may present the same problem you are experiencing).
On Tuesday, 9 October 2012 09:00:03 UTC-5, Bill Thayer wrote:
>
> WRT morning's Oracle error:
>
> Oracle hates long names so an identifier like
> PLUGIN_WIKI_PAGE_MODIFIED_BY_CONSTRAINT and
> PLUGIN_WIKI_ATTACHEMENT_MODIFIED_BY_CONSTRAINT both get shortened to
> PLUGIN_WIK_MODIFIE__CONSTRIANT so that creates a conflict on the second one.
>
> -Bill
>
> P.S.
>
> The plugin wiki code is nice. I wound up stripping out much of what I
> wrote for my app in favor of the wiki approached but the naming conventions
> are posing problems that newbies like myself are going to find difficult to
> understand. Then my challenge is to actually use the functionality properly
> in my app..
>
> On Tuesday, October 9, 2012 8:42:49 AM UTC-5, Bill Thayer wrote:
>>
>> That's a good suggestion. i was going to create the remaining tables in
>> SQL developer then run web2py with migrate=false.
>>
>> BTW. The tables I'm having my current problems with are the plug_wiki
>> tables. DAL managed to create PLUGIN_WIKI_PAGE but not
>> PLUGIN_WIKI_ATTACHEMENT. The error returned in the web2py ticket is
>> <class 'cx_Oracle.DatabaseError'> ORA-02264: name already used by an
>> existing constraint
>>
>>
>> A very nice piece of information would be WHICH CONSTRAINT? That's what I
>> *hate* about Oracle.
>>
>> Does anyone know if it's OK to change the name of this constraint (once I
>> find it) on the database side without breaking my web2py application?
>>
>> Regards,
>>
>> Bill
>>
>>
>> Try run
>>>
>>> python web2py.py -S welcome
>>>
>>> then do things manually
>>>
>>> >>> db = DAL('oracle://....',migrate=True)
>>> >>> db.define_tables('person',Field('name'))
>>>
>>> etc. See what goes wrong. If your want to access tables that are already
>>> there you set migrate=False but still need to define_table them.
>>>
>>> On Monday, 8 October 2012 21:08:58 UTC-5, Cliff Kachinske wrote:
>>>>
>>>> Can you connect to the database outside of Web2py?
>>>>
>>>> The long delay can mean connection problems, which I have induced by
>>>> typing the db name incorrectly.
>>>>
>>>> On Monday, October 8, 2012 8:06:58 PM UTC-4, Bill Thayer wrote:
>>>>>
>>>>> Hi Massimo,
>>>>>
>>>>> Thank you.
>>>>>
>>>>> After installing the latest version I deleted the contents of the
>>>>> databases folder and run with DAL(...,migrate=True) got one error, set
>>>>> the
>>>>> table causing the error to migrate=false and re-ran. Now all the database
>>>>> tables are created but now (after seting my settings.migrate to False in
>>>>> 0.py the browser just shows the spinner when I try to access my app's
>>>>> index
>>>>> page. The progress bar is shows only half progress.
>>>>>
>>>>> Regards,
>>>>> Bill
>>>>>
>>>>> On Monday, October 8, 2012 5:53:04 PM UTC-5, Massimo Di Pierro wrote:
>>>>>>
>>>>>> LOL
>>>>>>
>>>>>> - Make sure you use stable "Version 2.0.9 (2012-09-13 23:51:30)" of
>>>>>> the latest trunk. Not any intermediate version.
>>>>>> - do not use the wizard if you do not want crap. The wizard is
>>>>>> experimental and not the best piece of web2py.
>>>>>> - If your tables already exist and you are happy with them run onces
>>>>>> with db = DAL(....,fake_migrate=True) and then run with
>>>>>> DAL(...,migrate=false)
>>>>>> - If instead you want web2py to create tables and use migrations,
>>>>>> delete you database, re-create it empty, delete everything under
>>>>>> yourapp/databases/ and run with DAL(...,migrate=True).
>>>>>>
>>>>>> On Monday, 8 October 2012 17:33:06 UTC-5, Bill Thayer wrote:
>>>>>>>
>>>>>>> Ok,
>>>>>>>
>>>>>>> I have my Oracle database. From some attempted migrations I have the
>>>>>>> auth tables defined and two other tables defined of about 17 tables.The
>>>>>>> typical error is Object with that name already exists or some crap like
>>>>>>> that. I figured clicking the clean button would help... DON"T DO THAT!
>>>>>>> Now
>>>>>>> my browser just spins and spins.
>>>>>>>
>>>>>>> My SQL log has a bunch of crap that i do not want created in my
>>>>>>> database like archive tables that the wizard created. Yet if I delete
>>>>>>> the
>>>>>>> log file it will not re-create with a fresh log.
>>>>>>>
>>>>>>> After restoiring my backup my sql.log file has 2627 lines in it and
>>>>>>> the time stamps go back 6 days when I started this all from scratch.
>>>>>>>
>>>>>>> Without having to re-create my application again. How can i just get
>>>>>>> a nice clean SQL file and how, once connect to my DB can I get my new
>>>>>>> db.py
>>>>>>> or db_wizard.py definitions to make the database tables that aren't
>>>>>>> already
>>>>>>> created without throwing errors for the ones that already are?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
--
