CodeCharge
|
| Posted: 07/13/2001, 2:02 PM |
|
Hello,
CodeCharge Beta 2.0 Release 4 is now available at
http://www.codecharge.com/download/files/CodeCharge20BetaR4_Upg.exe
It generates ASP&Templates, PHP&Templates and Perl&Templates.
This release is being rushed out the door without being fully tested,
assuming that some of you are willing to take risks 
MyODBC crash issue is supposedly fixed and we'd like someone who had this
problem previously to confirm this.
Please backup your previous .ccs files because the new version may add new
attributes, not readable by version 1.x.
Three important changes from Release 2 are:
1. Database Properties now contains Design Connection String Type, "Custom"
or "DSN".
This allows CodeCharge to use different connection methods and was
implemented to resolve certain issues with database connectivity.
For example DSN method fixes the issue where PostgreSQL table names
containing undesrcores (_) weren't shown in CodeCharge.
2. Redesigned "JOIN" functionality.
a) In the Database Properties now you can specify the JOIN type that you
like to generate, either "ANSI SQL" or "Oracle (+= / =)"
This is often used in Grids where you want to display values from related
tables by specifying "JOIN" parameters.
Generating ANSI style SQL will use "JOIN" clause.
Generating Oracle style SQL will use "WHERE" clause.
Please refer to
http://www.sql-tutor.com/sql_tutor/students/lessons/lesson4.asp for
comparison.
b) In Field Properties JOIN section now you can specify "[x] Left Join".
This allows you to display records even if the related record in the 2nd
table doesn't exist.
If you specified ANSI style in the Database Properties, the generated code
will use "LEFT JOIN" clause.
If you specified Oracle standard, the generated code will use "WHERE ... +=
...." clause.
3. Form Input section has a new layout and contains new "Default Value"
field.
This default value is needed for using Input Parameters in custom SQL
queries, and will be fully implemented and described later.
Adam Stock
YesSoftware
CodeCharge Team
|
|
|
 |
Jeff Stuart
|
| Posted: 07/13/2001, 8:08 PM |
|
(WAHOO! :D) Downloading as we speak! I'll let ya guys know shortly!
--
Jeff Stuart
jstuart@neo.rr.com
"CodeCharge" <support@codecharge.com> wrote in message
news:9innka$2mq$1@news.codecharge.com...
> Hello,
>
> CodeCharge Beta 2.0 Release 4 is now available at
> http://www.codecharge.com/download/files/CodeCharge20BetaR4_Upg.exe
> It generates ASP&Templates, PHP&Templates and Perl&Templates.
> This release is being rushed out the door without being fully tested,
> assuming that some of you are willing to take risks
> MyODBC crash issue is supposedly fixed and we'd like someone who had this
> problem previously to confirm this.
> Please backup your previous .ccs files because the new version may add new
> attributes, not readable by version 1.x.
>
> Three important changes from Release 2 are:
> 1. Database Properties now contains Design Connection String Type,
"Custom"
> or "DSN".
> This allows CodeCharge to use different connection methods and was
> implemented to resolve certain issues with database connectivity.
> For example DSN method fixes the issue where PostgreSQL table names
> containing undesrcores (_) weren't shown in CodeCharge.
>
> 2. Redesigned "JOIN" functionality.
> a) In the Database Properties now you can specify the JOIN type that you
> like to generate, either "ANSI SQL" or "Oracle (+= / =)"
> This is often used in Grids where you want to display values from related
> tables by specifying "JOIN" parameters.
> Generating ANSI style SQL will use "JOIN" clause.
> Generating Oracle style SQL will use "WHERE" clause.
> Please refer to
> http://www.sql-tutor.com/sql_tutor/students/lessons/lesson4.asp for
> comparison.
> b) In Field Properties JOIN section now you can specify "[x] Left Join".
> This allows you to display records even if the related record in the 2nd
> table doesn't exist.
> If you specified ANSI style in the Database Properties, the generated code
> will use "LEFT JOIN" clause.
> If you specified Oracle standard, the generated code will use "WHERE ...
+=
> ..." clause.
>
> 3. Form Input section has a new layout and contains new "Default Value"
> field.
> This default value is needed for using Input Parameters in custom SQL
> queries, and will be fully implemented and described later.
>
> Adam Stock
> YesSoftware
> CodeCharge Team
>
>
>
|
|
|
|
Jeff Stuart
|
| Posted: 07/13/2001, 8:50 PM |
|
HOT F*CKIN D*MN! YOU GUYS GOT IT! ALRIGHT!!
Good job guys!!! It don't crash no more. :D
Oh wait, better have it generate code. :D
Yup! Even generated code! GOOD JOB!!!!
Ok.. got a small thing for me to fix (again. :D)
Note, in the common.php, it generates this code:
function db_fill_array($sql_query)
{
$db_fill = new DB_Sql();
$db_fill->Database = DATABASE_NAME;
$db_fill->User = DATABASE_USER;
$db_fill->Password = DATABASE_PASSWORD;
$db_fill->Host = DATABASE_HOST;
$db_fill->query($sql_query);
if ($db_fill->next_record())
{
do
{
$ar_lookup[$db_fill->f(0)] = $db_fill->f(1);
} while ($db_fill->next_record());
return $ar_lookup;
}
else
return false;
}
(and a little bit further down the road: )
function get_db_value($sql)
{
$db_look = new DB_Sql();
$db_look->Database = DATABASE_NAME;
$db_look->User = DATABASE_USER;
$db_look->Password = DATABASE_PASSWORD;
$db_look->Host = DATABASE_HOST;
$db_look->query($sql);
if($db_look->next_record())
return $db_look->f(0);
else
return "";
}
However, I created a custom connection. Which is this:
// CustomConnection Start
$db = new DB_Email();
// CustomConnection End
I think that your $db_look and $db_fill should use my custom connection.
Note, this happens in both 1.1 and 2.0.
Once I fixed that, it works like a champ!!!! I LOVE how you're doing the
paging now! THANK YOU GUYS!!!
IT WORKS! :D
(If you can't tell, I'm VERY happy with this now! :D)
--
Jeff Stuart
jstuart@neo.rr.com
"CodeCharge" <support@codecharge.com> wrote in message
news:9innka$2mq$1@news.codecharge.com...
> Hello,
>
> CodeCharge Beta 2.0 Release 4 is now available at
> http://www.codecharge.com/download/files/CodeCharge20BetaR4_Upg.exe
> It generates ASP&Templates, PHP&Templates and Perl&Templates.
> This release is being rushed out the door without being fully tested,
> assuming that some of you are willing to take risks
> MyODBC crash issue is supposedly fixed and we'd like someone who had this
> problem previously to confirm this.
> Please backup your previous .ccs files because the new version may add new
> attributes, not readable by version 1.x.
>
> Three important changes from Release 2 are:
> 1. Database Properties now contains Design Connection String Type,
"Custom"
> or "DSN".
> This allows CodeCharge to use different connection methods and was
> implemented to resolve certain issues with database connectivity.
> For example DSN method fixes the issue where PostgreSQL table names
> containing undesrcores (_) weren't shown in CodeCharge.
>
> 2. Redesigned "JOIN" functionality.
> a) In the Database Properties now you can specify the JOIN type that you
> like to generate, either "ANSI SQL" or "Oracle (+= / =)"
> This is often used in Grids where you want to display values from related
> tables by specifying "JOIN" parameters.
> Generating ANSI style SQL will use "JOIN" clause.
> Generating Oracle style SQL will use "WHERE" clause.
> Please refer to
> http://www.sql-tutor.com/sql_tutor/students/lessons/lesson4.asp for
> comparison.
> b) In Field Properties JOIN section now you can specify "[x] Left Join".
> This allows you to display records even if the related record in the 2nd
> table doesn't exist.
> If you specified ANSI style in the Database Properties, the generated code
> will use "LEFT JOIN" clause.
> If you specified Oracle standard, the generated code will use "WHERE ...
+=
> ..." clause.
>
> 3. Form Input section has a new layout and contains new "Default Value"
> field.
> This default value is needed for using Input Parameters in custom SQL
> queries, and will be fully implemented and described later.
>
> Adam Stock
> YesSoftware
> CodeCharge Team
>
>
>
|
|
|
|
Ann Harrell
|
| Posted: 08/09/2001, 8:04 AM |
|
CF and templates update?
Ann Harrell
"CodeCharge" <support@codecharge.com> wrote in message
news:9innka$2mq$1@news.codecharge.com...
> Hello,
>
> CodeCharge Beta 2.0 Release 4 is now available at
> http://www.codecharge.com/download/files/CodeCharge20BetaR4_Upg.exe
> It generates ASP&Templates, PHP&Templates and Perl&Templates.
> This release is being rushed out the door without being fully tested,
> assuming that some of you are willing to take risks
> MyODBC crash issue is supposedly fixed and we'd like someone who had this
> problem previously to confirm this.
> Please backup your previous .ccs files because the new version may add new
> attributes, not readable by version 1.x.
>
> Three important changes from Release 2 are:
> 1. Database Properties now contains Design Connection String Type,
"Custom"
> or "DSN".
> This allows CodeCharge to use different connection methods and was
> implemented to resolve certain issues with database connectivity.
> For example DSN method fixes the issue where PostgreSQL table names
> containing undesrcores (_) weren't shown in CodeCharge.
>
> 2. Redesigned "JOIN" functionality.
> a) In the Database Properties now you can specify the JOIN type that you
> like to generate, either "ANSI SQL" or "Oracle (+= / =)"
> This is often used in Grids where you want to display values from related
> tables by specifying "JOIN" parameters.
> Generating ANSI style SQL will use "JOIN" clause.
> Generating Oracle style SQL will use "WHERE" clause.
> Please refer to
> http://www.sql-tutor.com/sql_tutor/students/lessons/lesson4.asp for
> comparison.
> b) In Field Properties JOIN section now you can specify "[x] Left Join".
> This allows you to display records even if the related record in the 2nd
> table doesn't exist.
> If you specified ANSI style in the Database Properties, the generated code
> will use "LEFT JOIN" clause.
> If you specified Oracle standard, the generated code will use "WHERE ...
+=
> ..." clause.
>
> 3. Form Input section has a new layout and contains new "Default Value"
> field.
> This default value is needed for using Input Parameters in custom SQL
> queries, and will be fully implemented and described later.
>
> Adam Stock
> YesSoftware
> CodeCharge Team
>
>
>
|
|
|
|
|
