Gossamer Forum
Home : Products : Gossamer Links : Discussions :

New bug in LSQL working with PostgreSQL

Quote Reply
New bug in LSQL working with PostgreSQL In reply to
Hello TheStone / All

I found a new problem when I try to make a Category update in LSQL working with PostgreSQL. The problem is similar to the first one that I had reporting in this thread:

I have a tree category like:

Category1
Category1/Subcategory1
Category1/Subcategory2
Category1/Subcategory3
Category1/Subcategory4

Now if I move, copy or add new categories it works fine. The admin updates the database ans especialy the column "full_name". This were fixed ok!

But now, lets go to rename "Category1": Change the name to Category2 and show into database, the "full_name" column reads as follows (same example):

Category2
Category2/Subcategory1
Category2/Subcategory1
Category2/Subcategory1
Category2/Subcategory1

Please, note that Category2 field is updated successfull but the subcategory name didnīt! And in more complex example:

Category1
Category1/Subcategory1
Category1/Subcategory2/SubSubCategory3
Category1/Subcategory4/SubSubCategory5
Category1/Subcategory6

The result is:

Category2
Category2/Subcategory1
Category2/Subcategory1
Category2/Subcategory1
Category2/Subcategory1

I think that this is a big problem... Any help?

Thanks! :(
Subject Author Views Date
Thread 2 bugs in LSQL working with PostgreSQL avant 2112 Mar 10, 2003, 2:05 AM
Thread Re: [avant] 2 bugs in LSQL working with PostgreSQL
604 2038 Mar 18, 2003, 10:51 AM
Post Re: [TheStone] 2 bugs in LSQL working with PostgreSQL
avant 2017 Mar 22, 2003, 3:06 AM
Post New bug in LSQL working with PostgreSQL
avant 1982 Apr 6, 2003, 3:48 AM